On 26 February 2013 21:37, Daniel Frey wrote: > While using Clang++ 3.2 with libstdc++ from GCC 4.7, I ran into a problem which was discussed at StackOverflow <http://stackoverflow.com/q/15098174>. A fix in libstdc++ seems easily possible, but first: Should I create a bug report for things that actually work with GCC and only break with Clang? Or does libstdc++ accept only bugs exposed with GCC? Please report it to bugzilla, thanks.
