[Bug middle-end/113694] Allow renaming stack smashing protector symbols

2024-02-14 Thread matheus.a.m.moreira at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113694 --- Comment #4 from Matheus Afonso Martins Moreira --- (In reply to Sam James from comment #3) > Note that this isn't something GCC offers for other things, e.g. PR97119. GCC does offer it for at least one thing that I'm aware of: -e entry

[Bug middle-end/113694] Allow renaming stack smashing protector symbols

2024-02-01 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113694 Sam James changed: What|Removed |Added CC||sjames at gcc dot gnu.org See Als

[Bug middle-end/113694] Allow renaming stack smashing protector symbols

2024-02-01 Thread matheus.a.m.moreira at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113694 --- Comment #2 from Matheus Afonso Martins Moreira --- That's true but in that case the __stack_chk_* symbols will remain in the compiler output and in the final binary. They will show up in readelf output, GDB function disassemblies. I think t

[Bug middle-end/113694] Allow renaming stack smashing protector symbols

2024-02-01 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113694 --- Comment #1 from Richard Biener --- You could provide an alias to __stack_chk_guard/__stack_chk_fail in your code though.

[Bug middle-end/113694] Allow renaming stack smashing protector symbols

2024-01-31 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113694 Andrew Pinski changed: What|Removed |Added Severity|normal |enhancement