https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77488
R. Diez changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77488
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77488
Fangrui Song changed:
What|Removed |Added
CC||i at maskray dot me
--- Comment #8 from F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77488
--- Comment #7 from R. Diez ---
(In reply to Piotr Henryk Dabrowski from comment #6)
> You can use:
>
> #line 2 "FileName.cpp"
>
> at the very top (!) of all your files
> to change the content of __FILE__.
> This also affects compiler messages.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77488
Piotr Henryk Dabrowski changed:
What|Removed |Added
CC||phd at phd dot re
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77488
--- Comment #5 from Martin Sebor ---
> How would that help here? You obviously pass the address of the string
> literal to the __assert_func or how is the assertion passed, thus it escapes.
With the optimization in place the assert macro could
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77488
--- Comment #4 from Jakub Jelinek ---
(In reply to Martin Sebor from comment #3)
> Perhaps it might be possible to generalize the enhancement request to a
> space optimization for GCC to store only the trailing part of strings that
> are ever ref
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77488
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77488
--- Comment #2 from R. Diez ---
> __FILE__ expands to whatever you pass on the command line as the base file
> (and for headers whatever the directory is where they are found + the header
> filename. So, if you compile with gcc -c something.c -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77488
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
10 matches
Mail list logo
