[Bug debug/97060] New: Missing DW_AT_declaration=1 in dwarf data

2020-09-15 Thread jolsa at redhat dot com
Assignee: unassigned at gcc dot gnu.org Reporter: jolsa at redhat dot com Target Milestone: --- We are missing expected declaration tag - DW_AT_declaration : 1 for function in debug info data. The problem we see is: - fs/init.c calls vfs_getattr function - vfs_getattr is

[Bug debug/97060] Missing DW_AT_declaration=1 in dwarf data

2020-09-16 Thread jolsa at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97060 --- Comment #2 from Jiri Olsa --- Created attachment 49223 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49223&action=edit fs/init.i

[Bug debug/97060] Missing DW_AT_declaration=1 in dwarf data

2020-09-16 Thread jolsa at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97060 --- Comment #4 from Jiri Olsa --- (In reply to Jakub Jelinek from comment #3) > So this is really just something like: -O2 -g -dA: > extern int foo (unsigned int, unsigned int); > > int > bar (void) > { > foo (1, 2); > return 0; > } > > whe

[Bug debug/97060] Missing DW_AT_declaration=1 in dwarf data

2020-09-17 Thread jolsa at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97060 --- Comment #9 from Jiri Olsa --- (In reply to Jakub Jelinek from comment #6) > Also, to avoid confusion, upstream 10 branch is not affected, but in 10-RH > we've backported the PR96383 changes from the trunk. Is this gcc going to RHEL8? that co

[Bug debug/97060] Missing DW_AT_declaration=1 in dwarf data

2020-09-17 Thread jolsa at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97060 --- Comment #11 from Jiri Olsa --- (In reply to Jakub Jelinek from comment #10) > RHEL8 uses gcc 8 which is not affected (unless one uses DTS/GTS). > Also, it is unclear for what in particular pahole or what wants to use > DW_AT_declaration. pah

[Bug debug/97060] Missing DW_AT_declaration=1 in dwarf data

2020-10-14 Thread jolsa at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97060 --- Comment #13 from Jiri Olsa --- hi, any update on the fix? I'm seeing the bug now in fedora 32 with: $ gcc --version gcc (GCC) 10.2.1 20201005 (Red Hat 10.2.1-5) thanks, jirka