[Bug bootstrap/107728] with -O0, libgcc in the first stage compiler has reference to libc functions

2022-11-24 Thread arnout at mind dot be via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107728 --- Comment #5 from Arnout Vandecappelle --- Based on > glibc builds needs to be fixed such that it does not reference the function > in the unwinder at -O0 I've traced through the map file why this symbol is pulled in:

[Bug bootstrap/107728] with -O0, libgcc in the first stage compiler has reference to libc functions

2022-11-24 Thread arnout at mind dot be via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107728 Arnout Vandecappelle changed: What|Removed |Added CC||arnout at mind dot be ---

[Bug bootstrap/107728] with -O0, libgcc in the first stage compiler has reference to libc functions

2022-11-16 Thread thomas.petazzoni--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107728 --- Comment #3 from Thomas Petazzoni --- Thanks for the super quick feedback. Could you clarify "Move over, the functions are not optimized out at -O2 but rather they don't get pulled in glibc building because another function is referenced." ?

[Bug bootstrap/107728] with -O0, libgcc in the first stage compiler has reference to libc functions

2022-11-16 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107728 --- Comment #2 from Andrew Pinski --- Move over, the functions are not optimized out at -O2 but rather they don't get pulled in glibc building because another function is referenced. Either libgcc should be built with -fdata-sections

[Bug bootstrap/107728] with -O0, libgcc in the first stage compiler has reference to libc functions

2022-11-16 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107728 Andrew Pinski changed: What|Removed |Added Resolution|--- |MOVED Status|UNCONFIRMED