On undefined, Corey Osgood <corey.osgood@gmail.com> wrote:
On Wed, Apr 2, 2008 at 6:10 PM, Uwe Hermann <uwe@hermann-uwe.de> wrote:
On Wed, Apr 02, 2008 at 05:59:16PM -0400, Corey Osgood wrote:
> On Wed, Apr 2, 2008 at 5:12 PM, Stefan Reinauer <stepan@coresystems.de>
> wrote:
>
> > In addition, you could try using "unsigned" instead of "u8"... I think
> > romcc is kind of bad at handling different data types and it handles all
> > sizes equally (ie. using u8 does not gain you the rest of the register you
> > are using)
>
>
> Thanks, unsigned int/long, u16/u32, and int/long all still produce the same
> error (including the auto unsigned char part).

Try -mcpu=p2 (or other values) in romcc, e.g.

 action  "./romcc -mcpu=p2 -E -O -I$(TOP)/src -I. $(CPPFLAGS) $(MAINBOARD)/auto.c -o $@"

That helped last time I had the same problem. Depends on which
CPU/chipset you use, of course.


Uwe.

c3, c3-2, p2, p3, and p4 all give the same error. Same applies when -mmmx and/or -msse are added. -fdebug-all gives the same error too, no more info

Thanks,
Corey

Huh, well, the problem's gone now. I have no idea why it worked, but I changed the smbus functions along with the spd_read_byte wrapper from returning a u8 to an int. Makes no sense, but it works.

-Corey