On Fri, Jun 26, 2015 at 10:14:41AM +0000, Antti Kantee wrote: > As long as NetBSD's goals include "interoperates well with other systems" > and "conforms to open systems standards as much as is practical", the > workaround is mandated. It fixes source level interoperation with a > contemporary release of a major compiler (fact) and given that it's a few > lines to a single file, it's practical (subjective). Of course, I'd *like* > to go back in time to fix all bugs, but I'm not high on hopes with that > being possible.
We generally don't workaround standard compliance bugs in compilers, especially .0 releases with a history of being buggy. That said, have you verified why it doesn't happen with libstdc++ itself? I would somewhat suspect that the threatment of the header as system header hides the problem for libstdc++, I can't imagine that it can correctly implement the constexpr constructor without performance penalties otherwise... Joerg
