[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] TCC on new ARM EABI (ARMEL)

From: Cayle Graumann
Subject: Re: [Tinycc-devel] TCC on new ARM EABI (ARMEL)
Date: Sun, 17 Sep 2006 22:45:06 -0500


    Adding the extra set of parentheses in the define was the solution I came up with to get it to compile also.  The real question is why does GCC allow it?  The more I looked at it, the more convinced I am that it shouldn't. 

I'll see what I can do about the gen_opl function.  I haven't really spent enough time yet with going though the tcc code to get a feel for it at this time.

Thanks for all your help.


On 9/17/06, Daniel Glöckner <address@hidden> wrote:
On Sun, Sep 17, 2006 at 02:12:39PM -0500, Cayle Graumann wrote:
> #define nelem(x)        (sizeof (x)/sizeof (x)[0])

#define nelem(x)        (sizeof (x)/sizeof ((x)[0]))

parse_expr_type() needs the block after "/* post operations */" from
unary() after skip(')') when parse_btype() is false.

But then we can go further and ask if "sizeof (char)7" is a legal C

> static uvlong uvnan    = ((uvlong)0x7FF00000<<32)|0x00000001;

You need to implement the "if (c1 && c2)" block from gen_opic() in


Tinycc-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]