RE: [sdcc-devel] short issues....

[Sandeep D. <sa...@dd...>]

Johan,

I prefer short being a separate type by itself, which we can control the
sizeof etc etc...
not just a synonym for INT or CHAR

Sandeep

-----Original Message-----
From: sdc...@li...
[mailto:sdc...@li...]On Behalf Of Johan Knol
Sent: Monday, June 04, 2001 6:25 AM
To: sdc...@li...
Subject: [sdcc-devel] short issues....


I made SDCCval.c:constVal() create a char for values < 256 instead of a
short int. This is not (and should not be, but that's another story) the
same. E.g. after my latest fix of the cge optimizer, it decides that a bit
var does not have the same SPEC_SHORT as a constant and allows the terrible
cast:

static bit long_flag=0;

        mov     r2,#0x00
        mov     a,r2
        clr     c
        jz      00104$
        cpl     c
00104$:
        mov     _long_flag,c

instead of just:

    clr _long_flag

Even worse, the loop optimizer (since it now only sees invariant iTemp's for
e.g. radix in printfl.c) decides to take the assignments out of the loop.

The next step will be to remove _short from the specifier structure and
#define V_SHORT to either V_CHAR (as it is) or to V_INT (as it should be).

Comments are welcome.

Johan


_______________________________________________
sdcc-devel mailing list
sdc...@li...
http://lists.sourceforge.net/lists/listinfo/sdcc-devel