This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Speaking of DWARF-2 macro info


It appears we now (this didn't happen before) end up generating two start 
files for the same file.
But only one end file.
So the macro info looks like:
.byte   0x3      # Start new file
        .uleb128 0x0     # Included from line number 0
        .uleb128 0x1     # Filename we just started
        .byte   0x3      # Start new file
        .uleb128 0x0     # Included from line number 0
        .uleb128 0x1     # Filename we just started
...
     .byte   0x4      # End file

As one can see, the two start file lines are identical.

Either of you know why we see two starts?

The macro debug info outputter doesn't do anything special. It completely 
relies on the preprocessor stage to tell it when it sees the start of a 
new file/the end of a file/a define/an undefine.
So if we get two starts outputted, it means cpp is calling the hook twice.
--Dan


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]