complex-to-int comparison bug(s), any target including i686-pc-linux-gnulibc1

[Hans-Peter Nilsson]

Hi.

It seems gcc snapshot 980502 as well as the latest egcs snapshot
(version.c:egcs-2.91.26 19980502 (gcc2 ss-980401 experimental)) as do
gcc-2.7.2 and gcc-2.8.1 all SEGV on the following, with any and no
optimization-switches (no other switches):

int i2 = 0i != 10;
void doit(void)
{
 int i = 0i != 10;
}

The first line gives a "initializer element is not computable at load time"
which may or may not be a bug (the corresponding non-complex comparison seems
to be computable at load time...); I just stumbled upon it.

The second (run-time) comparison gives a SEGV through a NULL-pointer at
different places, depending on optimization switch.
 Further investigation si left to any parser-people (those who know the
tree:s)

Sidenote:  this originally came from a syntax error of the form
"for (i=0i!=10..."

brgds, H-P
-- 
Hans-Peter Nilsson, Axis Communications AB, S - 223 70 LUND, SWEDEN
Hans-Peter.Nilsson@axis.se | http://www.axis.se/ | Tel +46 462701867,2701800
Fax +46 46136130 | RFC 1855 compliance implemented; report loss of brain.