Thanks to visit codestin.com
Credit goes to postgrespro.com

Re: GIN FailedAssertions on Itanium2 with Intel compiler - Mailing list pgsql-hackers

From Teodor Sigaev
Subject Re: GIN FailedAssertions on Itanium2 with Intel compiler
Date
Msg-id [email protected]
Whole thread Raw
In response to Re: GIN FailedAssertions on Itanium2 with Intel compiler  (Martijn van Oosterhout <[email protected]>)
Responses Re: GIN FailedAssertions on Itanium2 with Intel
List pgsql-hackers
> What does that option do? Is it practical to enable it for the entire
> backend?From docs:
Disables inline expansion of standard library or intrinsic functions.

> And isn't this a straightforward compiler bug they should be notified
> about?
What's a choice? Now I see 3:
1) -O1
2) "volatile"
3) -nolib_inline

IMHO, only -O1 is guarantee for other possible places... But I'm not familiar 
enough with such kinds of bugs.

-- 
Teodor Sigaev                                   E-mail: [email protected]
  WWW: http://www.sigaev.ru/
 


pgsql-hackers by date:

Previous
From: "zhou bo"
Date:
Subject: about how to un-describe from pgsql-hackers
Next
From: Michael Glaesemann
Date:
Subject: Re: [PATCHES] Interval aggregate regression failure