Re: GIN FailedAssertions on Itanium2 with Intel compiler
От
Teodor Sigaev
Тема
Re: GIN FailedAssertions on Itanium2 with Intel compiler
Дата
Msg-id
44F81E18.7090909@sigaev.ru
Ответ на
Re: GIN FailedAssertions on Itanium2 with Intel compiler (Martijn van Oosterhout)
Список
Дерево обсуждения
GIN FailedAssertions on Itanium2 with Intel compiler "Sergey E. Koposov" <math@sai.msu.ru>
Re: GIN FailedAssertions on Itanium2 with Intel compiler Teodor Sigaev <teodor@sigaev.ru>
Re: GIN FailedAssertions on Itanium2 with Intel compiler Teodor Sigaev <teodor@sigaev.ru>
Re: GIN FailedAssertions on Itanium2 with Intel compiler Teodor Sigaev <teodor@sigaev.ru>
Re: GIN FailedAssertions on Itanium2 with Intel compiler Martijn van Oosterhout <kleptog@svana.org>
Re: GIN FailedAssertions on Itanium2 with Intel compiler Teodor Sigaev <teodor@sigaev.ru>
Re: GIN FailedAssertions on Itanium2 with Intel Bruce Momjian <bruce@momjian.us>
Re: GIN FailedAssertions on Itanium2 with Intel compiler "Sergey E. Koposov" <math@sai.msu.ru>
Re: GIN FailedAssertions on Itanium2 with Intel Bruce Momjian <bruce@momjian.us>
Re: GIN FailedAssertions on Itanium2 with Intel compiler Teodor Sigaev <teodor@sigaev.ru>
> 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: teodor@sigaev.ru WWW: http://www.sigaev.ru/
В списке pgsql-hackers по дате отправления