Re: [avr-gcc-list] dtostrf and the dreaded relocation truncated to fit: R_AVR_13_PCREL error

2007-04-06 Thread Dmitry K.
On Friday 06 April 2007 17:10, rtwas wrote: gcc: avr-gcc (GCC) 4.1.1 libc: avr-libc-1.4.4 [...] /usr/local/atmel/bin/avr-gcc -g -Os -Wall -mcall-prologues -mmcu=atmega128 -save-temps main.o spim.o spim_tmr0.o diag.o uart.o cmd.o cmd_spi.o -o avr_sdiag0.obj

Re: [avr-gcc-list] New GCC warning - how to silence?

2007-04-06 Thread Dmitry K.
It is interesting, what was a reason to declare default char as signed for AVR port? Many other GCC ports use unsigned. I find only one CPU that is suitable for such choice: PDP-11, where the shortest method to read memory (mov_byte_from_memory_to_register) expands a sign bit. Dmitry.

Re: [avr-gcc-list] New GCC warning - how to silence?

2007-04-06 Thread Lars Noschinski
* larry barello [EMAIL PROTECTED] [07-04-06 09:01]: Ok, this is the most interesting answer and begs another question: Are you just saying use either signed or unsigned (I typically use uint8_t except when the signedness counts) or is char a distinct type that has defined behavior across

RE: [avr-gcc-list] dtostrf and the dreaded relocation truncated to fit: R_AVR_13_PCREL error

2007-04-06 Thread Eric Weddington
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] org] On Behalf Of Dmitry K. Sent: Friday, April 06, 2007 1:15 AM To: avr-gcc-list@nongnu.org Subject: Re: [avr-gcc-list] dtostrf and the dreaded relocation truncated to fit: R_AVR_13_PCREL error On

Re: [avr-gcc-list] New GCC warning - how to silence?

2007-04-06 Thread Joerg Wunsch
As larry barello wrote: Are you just saying use either signed or unsigned (I typically use uint8_t except when the signedness counts) or is char a distinct type that has defined behavior across portable systems? char is always either signed or unsigned, but as a portable application must not

RE: [avr-gcc-list] New GCC warning - how to silence?

2007-04-06 Thread Eric Weddington
It is interesting, what was a reason to declare default char as signed for AVR port? Right now, there *is* a reason: consistency. We've always had it that way. Many other GCC ports use unsigned. I guess Denis inherited it from the i386 port that also defaults to signed

Re: [avr-gcc-list] New GCC warning - how to silence?

2007-04-06 Thread Rolf Magnus
On Freitag, 6. April 2007, Lars Noschinski wrote: * larry barello [EMAIL PROTECTED] [07-04-06 09:01]: Ok, this is the most interesting answer and begs another question: Are you just saying use either signed or unsigned (I typically use uint8_t except when the signedness counts) or is char a

Re: [avr-gcc-list] New GCC warning - how to silence?

2007-04-06 Thread Rolf Magnus
On Freitag, 6. April 2007, Eric Weddington wrote: I found it in avr.h of the port: #define DEFAULT_SIGNED_CHAR 1 So this means that the AVR defaults to a signed char. Can we change this to be unsigned?: Why? ___ AVR-GCC-list mailing list

Re: [avr-gcc-list] New GCC warning - how to silence?

2007-04-06 Thread Joerg Wunsch
As Eric Weddington wrote: The makefile explicitly compiles with -funsigned-chars Which just doesn't matter at all. , yet this produces a warning. Sure. It's a deficiency of the old compiler to *not* have produced that warning. Note that the issue seems to be when it is a pointer to a