Tom Lane <tgl@sss.pgh.pa.us> writes:
> "kanchana" <pkkanchana@gmx.net> writes:
> > gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -I../../../../src/
> > include -I/home/saratha/krb5/include -I/usr/local/ssl/include -c -o float.o
> > float.c
> > float.c: In function `float4out':
> > float.c:233: Internal compiler error in emit_move_insn, at expr.c:2739
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>
> Please observe that gcc's failure message tells you to report it to the
> gcc project. This is not Postgres' problem.
If you see the same bug repeatably it's a gcc bug. but if you see a different
message each time you try to compile it's more likely you have bad memory in
the machine. It's worth running a memory checker like memtest86 anyways, it
can't hurt. Bad memory is really quite common.
--
greg