Is there a way those of us that haven't setup the GCC compiler to make our own
MSPGCC
builds could get a _newer_ version of MSPGCC on the sf.net site? The latest
there is
over 6 months old.
Thanks
-Mark Stokes
On Mon, Dec 15, 2003 at 10:52:27PM +0300, Dmitry wrote:
> I think it's been fixed ages ado... can't remember when...
> however, conversion from unsigned to signed may result in negative value of
> destination if MSB of source is set in 1.
Ok, when I have my linux machine running I will check it a
I think it's been fixed ages ado... can't remember when...
however, conversion from unsigned to signed may result in negative value of
destination if MSB of source is set in 1.
~d
On Monday 15 December 2003 22:46, Matthias Weingart wrote:
> Hi Dimitry,
>
> run the software below and at the end
Hi Dimitry,
run the software below and at the end you get x=1 (should be 0!!)
It seems that gcc uses the flags of sub for the next if(); but it should do
a additional cmp !! (first it is a unsigned operation, then a signed)
msp430-gcc main.c -mmcu=msp430x149 -g -O2 -ffunction-sections
-Wl,--gc-
Oh sorry, I misunderstood you. I need to have the option -uInterruptVector!
Good to know, something for the docs.
M.
On Mon, Dec 15, 2003 at 12:02:56PM +0300, Dmitry wrote:
> Again, do not forget -Wl,-uInterruptVector !!!
> I just tried:
> msp430-gcc m.c -mmcu=msp430x149 -O2 -ffunction-sec
Again, do not forget -Wl,-uInterruptVector !!!
I just tried:
msp430-gcc m.c -mmcu=msp430x149 -O2 -ffunction-sections
-Wl,--gc-sections
-Wl,-uInterruptVectors -o main.elf -g
And it works fine.
~d
On Monday 15 Dece
On Mon, Dec 15, 2003 at 11:26:14AM +0300, Dmitry wrote:
>
> As simple as:
> -ffunction-sections -Wl,--gc-sections -Wl,-uInterruptVectors
Thx ~d, I tried the first options, but as I wrote in a previous posting
there must be something wrong. The failure is in the elf-file.
The debugger cannot load
> Hi listmembers,
>
> sorry to bother you again :-).
>
> With -O0 (no optimisation) static inline does not work?
> Is this true?
>
Don't use "-O0" - it makes debugging harder. When you specify no
optomisation, there is a great deal of extra code, which makes it very hard
to follow the generated a
As simple as:
-ffunction-sections -Wl,--gc-sections -Wl,-uInterruptVectors
BUT...
use with care. If you miss third option to gcc, you lose all interrupt
functions and a startup code. Also, if you're playing with c++, all global
constructors/destructors will be eliminated.
~d
On Sunday 14 De
