[Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category

2015-06-06 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438 --- Comment #2 from Andrew Pinski pinskia at gcc dot gnu.org --- (In reply to Andreas Schwab from comment #1) You always need to use the libstdc++ that is bundled with the compiler. Actually that is true but that does not make this bug a valid

[Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category

2015-06-06 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438 Andreas Schwab sch...@linux-m68k.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category

2015-06-06 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438 --- Comment #3 from Jonathan Wakely redi at gcc dot gnu.org --- Indeed. Before gcc-5 it was never supported to combine C++11 objects compiled with different major versions. The whole point of calling C++11 support experimental was that we

[Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category

2015-06-06 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438 James Y Knight foom at fuhm dot net changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED

[Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category

2015-06-06 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438 Jonathan Wakely redi at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category

2015-06-06 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438 --- Comment #7 from Jonathan Wakely redi at gcc dot gnu.org --- If you can provide a patch that makes it work without any unwanted side effects then I'll certainly look at it, but mixing versions for C++11 code is unsupported, and so I'm not

[Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category

2015-06-06 Thread costamagnagianfranco at yahoo dot it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438 --- Comment #4 from Gianfranco costamagnagianfranco at yahoo dot it --- The problem actually is Debian has gcc-4.9 as default compiler, and the libstdc++ provided in testing is from gcc-5.

[Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category

2015-06-06 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438 --- Comment #8 from Jonathan Wakely redi at gcc dot gnu.org --- Created attachment 35708 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=35708action=edit Compare old and new categories This fixes this specific testcase, but not all cases (if

[Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category

2015-06-06 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438 --- Comment #9 from James Y Knight foom at fuhm dot net --- What good is having special code to allow linking compatibility, if the program then can't work anyways? Isn't that anti-useful? I didn't realise you were the maintainer and knew

[Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category

2015-06-06 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438 James Y Knight foom at fuhm dot net changed: What|Removed |Added CC||doko at gcc dot