Wim Lewis w...@.org wrote:
I had thought that __FUNCTION__ and __PRETTY_FUNCTION__ acted like
string literals and could be used this way, but I just tested and they
seem to act like __func__.
__FUNCTION__ just predates the (C99) standardized __func__ but is
otherwise the same. Thus, it's
2012/4/30 Joerg Wunsch j...@uriah.heep.sax.de:
As this is debugging-only stuff, the way around is probably to just
use a CPU with enough RAM for debugging.
Yeah.
RAM shortage problem is nonsolvable by nature! :)
Well. It seems, that there isn't a simple way to place function name to and
get
AVR-LIbC's ISR-macros lead to confusing results for code like, e.g.
#include avr/io.h
#include avr/interrupt.h
void *p;
ISR (ADC_vect, ISR_NOBLOCK)
{
char c[10];
p = c;
}
which resolves a.a. to
void __vector_21 (void)
__attribute__ ((signal,used,externally_visible))
-Original Message-
From: avr-gcc-list-bounces+eric.weddington=atmel@nongnu.org [mailto:avr-
gcc-list-bounces+eric.weddington=atmel@nongnu.org] On Behalf Of Georg-
Johann Lay
Sent: Monday, April 30, 2012 9:03 AM
To: avr-gcc-list@nongnu.org
Cc: Jörg Wunsch
Subject:
Weddington, Eric schrieb:
Johann Lay
AVR-LIbC's ISR-macros lead to confusing results for code like, e.g.
#include avr/io.h
#include avr/interrupt.h
void *p;
ISR (ADC_vect, ISR_NOBLOCK)
{
char c[10];
p = c;
}
which resolves a.a. to
void __vector_21 (void)
__attribute__
