http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48301
--- Comment #4 from Mike Stump <mikestump at comcast dot net> 2011-03-28 17:41:36 UTC --- If there is an easy work around in gcc to avoid the problem, we could entertain that, but, generally, I'd be more interested in clang failures going forward. llvm-gcc is old and getting older every day. The dragon egg bits are newer and more compelling.