[Bug c/112812] New: Regression: ASAN + stack-protector breaks alignment of stack variables

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112812 Bug ID: 112812 Summary: Regression: ASAN + stack-protector breaks alignment of stack variables Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: norma

[Bug lto/101625] New: ICE in modref_tree::merge with LTO and -m32

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101625 Bug ID: 101625 Summary: ICE in modref_tree::merge with LTO and -m32 Product: gcc Version: 11.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lt

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

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

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

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

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

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 lto/101473] LTO makes debug info depend on toolchain path

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #6 from tonyb at cybernetics dot com --- 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.

[Bug lto/101473] LTO makes debug info depend on toolchain path

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #4 from tonyb at cybernetics dot com --- By "reproducible" I meant that with your test program, the binary output was the same regardless of the toolchain path as in https://reproducible-builds.org/, so the "problem" was not reproduce

[Bug lto/101473] LTO makes debug info depend on toolchain path

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 --- Comment #3 from tonyb at cybernetics dot com --- The output is reproducible for me with that test program too. Try this program instead: #include #include int main(int argc, char **argv) { if (freopen("/dev/null", "w", stdout) == NULL)

[Bug lto/101473] New: LTO makes debug info depend on toolchain path

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 Bug ID: 101473 Summary: LTO makes debug info depend on toolchain path Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: