[Bug c++/52477] New: Wrong initialization order? __attribute__((constructor)) vs static data access

2012-03-04 Thread przemoc at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52477 Bug #: 52477 Summary: Wrong initialization order? __attribute__((constructor)) vs static data access Classification: Unclassified Product: gcc Version: 4.7.0 Status:

[Bug c++/52477] Wrong initialization order? __attribute__((constructor)) vs static data access

2012-03-04 Thread przemoc at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52477 --- Comment #3 from Przemysław Pawełczyk 2012-03-04 14:24:10 UTC --- Thanks for solution, but... Isn't such order obvious or isn't it at least the most widely used one? I mean that by default static data initialization should precede constructor

[Bug c/28575] misleading __builtin_choose_expr documentation error

2010-11-29 Thread przemoc at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28575 Przemysław Pawełczyk changed: What|Removed |Added CC||przemoc at gmail dot com

[Bug c/46711] New: __builtin_choose_expr checks not chosen expression

2010-11-29 Thread przemoc at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46711 Summary: __builtin_choose_expr checks not chosen expression Product: gcc Version: 4.4.5 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: una

[Bug c/46711] __builtin_choose_expr checks not chosen expression

2010-11-29 Thread przemoc at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46711 --- Comment #3 from Przemysław Pawełczyk 2010-11-29 20:07:20 UTC --- Andrew, thanks for the always_inline hint. But weren't you too fast with marking PR 46711 as duplicate of PR 19449? Check which lines are marked with errors. 8th line is not me