Re: 8.3.3 compiler warnings with gcc 4.3 - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: 8.3.3 compiler warnings with gcc 4.3
Date
Msg-id 87od2poh5s.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: 8.3.3 compiler warnings with gcc 4.3  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> writes:

> Devrim GÜNDÜZ <devrim@gunduz.org> writes:
>> I'm getting these on Fedora-9:
>> tqual.c:115: warning: inlining failed in call to ‘SetHintBits’: call is
>
> They're just cosmetic.  We don't generally worry about fixing cosmetic
> warnings in back branches.

Are they? It seems like these were marked inline for a reason. SetHintBits has
at least one conditional in it which can often be optimized out (it's either
InvalidTransactionId or else has been tested already).

In the tuplestore case there's not much point in having that function if it's
not going to be inlined. I'm imagining that it was put in because someone did
verify that the non-inlined version was consuming significant time. -- Perhaps
a bit assumption though.

Also, is 8.3 really a "back branch"? It's the current release and anyone
downloading Postgres from source on the web site will be getting these
warnings -- and there are a lot of them. Enough that it looks like something's
gone wrong with the build.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services!


pgsql-hackers by date:

Previous
From: "Fujii Masao"
Date:
Subject: Mechanism to transmit multiple event notifications with one signal
Next
From: Simon Riggs
Date:
Subject: Re: rmgr hooks and contrib/rmgr_hook