Re: What to do with inline warnings?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: What to do with inline warnings?
Date: 2008-05-14 16:45:49
Message-ID: 21212.1210783549@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> What do we do with warnings generated by -Winline?

I believe we just put that in to see how many places inlining was being
done or not. If you want to compile with -Werror you'd better take it out.

> tqual.c: In function HeapTupleSatisfiesVacuum:
> tqual.c:88: error: inlining failed in call to SetHintBits: call is unlikely and code size would grow
> tqual.c:1057: error: called from here
> tqual.c:88: error: inlining failed in call to SetHintBits: call is unlikely and code size would grow
> tqual.c:1061: error: called from here

Hmm, it's a bit disturbing that the compiler is taking it upon itself to
decide that these calls are "unlikely".

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-05-14 17:02:06 Placement for a /port sort of include file?
Previous Message Alvaro Herrera 2008-05-14 16:44:11 Re: Re: [COMMITTERS] pgsql: Improve logic for finding object files on OBJS lines in contrib