https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63760
--- Comment #6 from Pierre Colombier ---
by the way a true "immediate constant" version of __func__ just like __FILE__
would be cool, even for non-avr platforms.
I know this is the old behaviour of __FUNCTION__ and that this has been changed
lon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63760
Pierre Colombier changed:
What|Removed |Added
CC||pcdwarf at pcdwarf dot net
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63760
--- Comment #4 from mojo at world3 dot net ---
I agree, a separate __funcP__is the best option.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63760
Georg-Johann Lay changed:
What|Removed |Added
Target|AVR |avr
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63760
--- Comment #2 from mojo at world3 dot net ---
On platforms with this kind of architecture the default is to place everything
in RAM, unless you specifically state otherwise.
With Harvard style architectures different instructions are used to acc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63760
--- Comment #1 from Andreas Schwab ---
Why aren't read-only data being placed in progmem by default?
