Re: 64 bit PostgreSQL 8.3.6 build on AIX 5300-09-02-0849 with IBM XL C/C++ 10.1.0.1 - initdb fails (could not dump unrecognized node type: 650)

The system and compiler are patched with the latest fix packs from IBM, and the compiler version is the latest
available.<br /><br />The compiler is functional (eg: I was able to compile successfuly 64 bit versions other software
suchas Apache 2.2.11, emacs 22.3, vim 7.2, openssl-0.9.8j and so on, all with similar flags).<br /><br />So if this is
acompiler bug, it certainly isn't an obvious one. I'll dig deeper to see how I can convince configure to use
-qnooptimize.<br/><br />The first build was using default options for xlC_r (the default for all IBM compilers is
-qnooptimize)../configure seems to override this:<br /><br />When I've used the build farm scripts, configure gives
xlC_rthese flags:<br /><br />configure:7117: xlC_r -q64 -o conftest -O2 -qmaxmem=16384 -qsrcmsg -qlonglong -g 
-I/opt/freeware/include/libxml2  -L/opt/freeware/lib  conftest.c -lm  >&5<br /> 1506-396 (W) Option -qlonglong
isincompatible with option -qlanglvl=extc99 and is ignored.<br />ld: 0711-317 ERROR: Undefined symbol: .setproctitle<br
/>ld:0711-345 Use the -bloadmap or -bnoquiet option to obtain more information.<br /> configure:7123: $? = 8<br /><br
/>I'lltry a 32 bit build too.<br /><br /><div class="gmail_quote">On Mon, Feb 9, 2009 at 8:58 AM, Tom Lane <span
dir="ltr"><<ahref="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>></span> wrote:<br /><blockquote
class="gmail_quote"style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;"><divclass="Ih2E3d">Mihai Criveti <<a href="mailto:cmihai@boreas.ro">cmihai@boreas.ro</a>> writes:<br />
>creating system views ... WARNING:  could not dump unrecognized node type:<br /> > 650<br /> > WARNING:
 couldnot dump unrecognized node type: 650<br /> > WARNING:  could not dump unrecognized node type: 650<br /> >
WARNING: could not dump unrecognized node type: 650<br /> > WARNING:  could not dump unrecognized node type: 650<br
/>> WARNING:  could not dump unrecognized node type: 650<br /> > WARNING:  could not dump unrecognized node type:
650<br/> > WARNING:  could not dump unrecognized node type: 650<br /> > WARNING:  could not dump unrecognized
nodetype: 650<br /> > WARNING:  could not dump unrecognized node type: 650<br /> > WARNING:  could not dump
unrecognizednode type: 650<br /> > FATAL:  badly formatted node string "} {} {} {} {} {} {} {} {} {} {})"...<br
/><br/></div>My, that's interesting.  A look at nodes.h shows that 650 == T_Value,<br /> which simply should not ever
occuras a live node type.  Unless my grep<br /> is missing something, T_Value itself is never directly referenced<br />
anywherein the 8.3 source code.  There are five occurrences of<br /> makeNode(Value) but each of them immediately
overwritesthe node type<br /> field with another type code such as T_Integer or T_String.<br /><br /> Not to put too
finea point on it, but I'm thinking "compiler bug".<br /> You might try a build with the optimization level backed off
tosee<br /> if the problem goes away.<br /><br />                        regards, tom lane<br /></blockquote></div><br
/><brclear="all" /><br />-- <br />Criveti Mihai<br /><a
href="http://unixsadm.blogspot.com">http://unixsadm.blogspot.com</a><br/><br />