Open awvwgk opened 3 years ago
No, fypp never adds line breaks to line markers. What can happen, that a line marker appears before a continuation line (as it is the case above), which ifort can not handle. You can switch this with the --line-numbering-mode=nocontlines
option. Unfortunately, it will not eliminate all the cases, as it will still result in line markers in two cases:
#:
directive appears after a continuation line:
subroutine some_routine(some_arg,&
#:if SOME_COND
& conditional_arg,&
#:endif
&)
#:block
/ #:call
statement has continuation lines in its argument:
#:block DEBUG
some_content&
&with_continuation line
#:endblock
Unfortunately, both cases seem to appear in DFTB+. The first one would have to big fixed in DFTB+, probably. The second one I would have to fix within fypp.
I'm trying to debug a segfault for a new library in DFTB+ using Intel oneAPI. To get a meaningful traceback I would like to emit line markers with
fypp
butifort
likes non of the available options.Using the
cpp
format the line markers are ignored due to bad formatWhile I get the an error with
std
formatted line markersNot sure what is going on here, but it seems to that fypp adding linebreaks in the line markers?