https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82176
--- Comment #10 from Gregory Fuchedzhy ---
(In reply to f.hollerer from comment #8)
> To my understanding assert() uses __FILE__ and __LINE__. I would like to
> have a command line option which let __FILE__ expand to the last path
> component (th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91812
--- Comment #13 from Gregory Fuchedzhy ---
(In reply to Richard Biener from comment #12)
> Fixed.
Thanks a lot, Richard!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82176
--- Comment #5 from Gregory Fuchedzhy ---
(In reply to Eric Gallager from comment #3)
> *** Bug 91998 has been marked as a duplicate of this bug. ***
Not exactly a duplicate, but related.
Clang implemented an additional __FILE_NAME__ macro.
See
: unassigned at gcc dot gnu.org
Reporter: fuchedzhy at google dot com
Target Milestone: ---
It would be handy to have macro similar to __FILE__ but expanding to source
*base* file name only.
It might be useful for application logs and asserts, especially on embedded
systems, where we don
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91812
--- Comment #2 from Gregory Fuchedzhy ---
(In reply to Eric Gallager from comment #1)
> If you declare ptr like this instead, the assembly comes out looking
> different:
> volatile unsigned int *volatile ptr;
Even seemingly unrelated code change
Assignee: unassigned at gcc dot gnu.org
Reporter: fuchedzhy at google dot com
Target Milestone: ---
GCC appears to ignore volatile modifier sometimes. C is probably wrong
component for the bug, but I'm not sure where else to put it.
$ arm-linux-gnueabi-gcc-8 -v
Using built-in