[Bug debug/101473] debug_line info depends on toolchain path

2021-11-09 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 Richard Biener changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-21 Thread tonyb at cybernetics dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #21 from tonyb at cybernetics dot com --- I tried adding -f*-prefix-map to LDFLAGS in Yocto, and that makes everything I tested binary reproducible, except for some shared libraries in /lib and /usr/lib because libtool filters out the

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-21 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #20 from Jakub Jelinek --- I think in DWARF for compilation units DW_AT_comp_dir is not optional.

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-21 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #19 from Richard Biener --- I think it is a bug - -fdebug-prefix-map should be fully reflected in the LTO IL and thus we should not end up creating un-remapped references to files (we should not create many references to files late a

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-20 Thread tonyb at cybernetics dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #18 from tonyb at cybernetics dot com --- Created attachment 51181 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51181&action=edit LTO reproducible build test: -ffile-prefix-map in LDFLAGS tar xjf lto-test.tar.bz2 cd lto-test

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-20 Thread tonyb at cybernetics dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #17 from tonyb at cybernetics dot com --- (In reply to Richard Biener from comment #16) > I'm interested if remaining differences are due to the same underlying issue > or not I tested your updated patch with gcc 10.2 (I had to make

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-20 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #16 from Richard Biener --- I'm interested if remaining differences are due to the same underlying issue or not, so I'm for now leaving this PR open (it's too late to backport for 11.2 but could be backported for 11.3 though it isn't

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-20 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #15 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:7cc2df084b7977653a9b59cbc34a9ad500ae619c commit r12-2412-g7cc2df084b7977653a9b59cbc34a9ad500ae619c Author: Richard Biener Date:

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-20 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 Richard Biener changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-20 Thread rguenther at suse dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #13 from rguenther at suse dot de --- On Mon, 19 Jul 2021, tonyb at cybernetics dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 > > --- Comment #12 from tonyb at cybernetics dot com --- > The patch fixed my own

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-19 Thread tonyb at cybernetics dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #12 from tonyb at cybernetics dot com --- The patch fixed my own programs, so I rebuilt all of Yocto with -flto in two different directories. I found that most shared libraries in /lib and /usr/lib still have the problem (i.e. are st

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-19 Thread tonyb at cybernetics dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #11 from tonyb at cybernetics dot com --- That change fixed the simple test program. Next I will try a more complex program, but it will take a while for everything to compile.

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-19 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #10 from Richard Biener --- (In reply to Richard Biener from comment #9) > (In reply to Richard Biener from comment #8) > > (In reply to tonyb from comment #6) > > > The only thing I know is that roughly similar issues were handled w

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-19 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #9 from Richard Biener --- (In reply to Richard Biener from comment #8) > (In reply to tonyb from comment #6) > > The only thing I know is that roughly similar issues were handled with the > > -fdebug-prefix-map=old=new switch, but I

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-19 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #8 from Richard Biener --- (In reply to tonyb from comment #6) > The only thing I know is that roughly similar issues were handled with the > -fdebug-prefix-map=old=new switch, but I am not the expert. Yes, that works to strip the i

[Bug debug/101473] debug_line info depends on toolchain path

2021-07-19 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 Richard Biener changed: What|Removed |Added Summary|LTO makes debug info depend |debug_line info depends on