Mon, 20 Dec 2004 14:28:06 -0500 (EST)
> The regressions all worked, but probably b/c there was not enough code to
> trip over gcc's optimization.
Probably a fair assesment.
> Anyways, the generated C code does not follow
> the aliasing rules of C, so that is certainly a bug too.
I don't know if there is a reasonable path to acheiving C aliasing rules;
or, rather, one that doesn't simply require inserting sufficient char*
casts to get the affect of -fno-strict-aliasing.
> I think a good goal for the c-codegen would be to replace '-w' with
> '-Wall -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings' and
> solve all of the resulting warnings...
Probably a very difficult task. But, maybe not impossible.