[Bug c/105510] error: initializer element is not constant

2024-07-04 Thread matheus.a.m.moreira at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105510 --- Comment #6 from Matheus Afonso Martins Moreira --- Also ran into this issue today, also involving compound literals in nested structure initialization macros. Because clang accepts this, it compiled fine on my development machine but failed

[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 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/93509] Stack protector should offer trap-only handling

2024-01-31 Thread matheus.a.m.moreira at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93509 --- Comment #3 from Matheus Afonso Martins Moreira --- Equivalent feature request in the LLVM issue tracker: https://github.com/llvm/llvm-project/issues/80236

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

2024-01-31 Thread matheus.a.m.moreira at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113694 Bug ID: 113694 Summary: Allow renaming stack smashing protector symbols Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug middle-end/93509] Stack protector should offer trap-only handling

2024-01-31 Thread matheus.a.m.moreira at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93509 Matheus Afonso Martins Moreira changed: What|Removed |Added CC||matheus.a.m.moreira at g

[Bug c/112840] feature request: warn on incorrect tagged union value access

2024-01-29 Thread matheus.a.m.moreira at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112840 --- Comment #3 from Matheus Afonso Martins Moreira --- (In reply to uecker from comment #2) > I would go for a more generic feature where one can specify some invariant / > condition that needs be true when a member of a struct / union is access

[Bug c/112840] New: feature request: warn on incorrect tagged union value access

2023-12-03 Thread matheus.a.m.moreira at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112840 Bug ID: 112840 Summary: feature request: warn on incorrect tagged union value access Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal