[Bug libstdc++/78905] Add a macro to determine that the library is implemented

2017-07-07 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78905 Jonathan Wakely changed: What|Removed |Added CC||coypu at sdf dot org --- Comment #11 f

[Bug libstdc++/78905] Add a macro to determine that the library is implemented

2017-01-22 Thread egall at gwmail dot gwu.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78905 Eric Gallager changed: What|Removed |Added CC||egall at gwmail dot gwu.edu --- Comment

[Bug libstdc++/78905] Add a macro to determine that the library is implemented

2017-01-19 Thread mattyclarkson at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78905 --- Comment #9 from Matt Clarkson --- (In reply to Jonathan Wakely from comment #7) > GCC 7 now defines _GLIBCXX_RELEASE (with the same value as __GNUC__ has, > i.e. the GCC major version, as an integer constant, but defined by the > library head

[Bug libstdc++/78905] Add a macro to determine that the library is implemented

2017-01-19 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78905 --- Comment #8 from Jonathan Wakely --- (In reply to Matt Clarkson from comment #2) > Because wehen I compile with clang against the libstdc++ the problem will > still occur and __GNUC__ will not be defined. N.B. Clang does define __GNUC__ but i

[Bug libstdc++/78905] Add a macro to determine that the library is implemented

2017-01-19 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78905 Jonathan Wakely changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libstdc++/78905] Add a macro to determine that the library is implemented

2017-01-19 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78905 --- Comment #6 from Jonathan Wakely --- Author: redi Date: Thu Jan 19 16:40:46 2017 New Revision: 244642 URL: https://gcc.gnu.org/viewcvs?rev=244642&root=gcc&view=rev Log: PR78905 define _GLIBCXX_RELEASE macro PR libstdc++/78905

[Bug libstdc++/78905] Add a macro to determine that the library is implemented

2016-12-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78905 Jonathan Wakely changed: What|Removed |Added Status|RESOLVED|NEW Last reconfirmed|

[Bug libstdc++/78905] Add a macro to determine that the library is implemented

2016-12-22 Thread mattyclarkson at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78905 --- Comment #4 from Matt Clarkson --- That's OK. I'm not particularly looking for the macro to be backported to 4.9. Just as we move forward the new macro is available. If not it's not the end of the world I can always maintain the snippet intern

[Bug libstdc++/78905] Add a macro to determine that the library is implemented

2016-12-22 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78905 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/78905] Add a macro to determine that the library is implemented

2016-12-22 Thread mattyclarkson at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78905 --- Comment #2 from Matt Clarkson --- Because wehen I compile with clang against the libstdc++ the problem will still occur and __GNUC__ will not be defined. This happens on any distro where GCC is the default but ships clang as an alternative co

[Bug libstdc++/78905] Add a macro to determine that the library is implemented

2016-12-22 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78905 --- Comment #1 from Andrew Pinski --- Why don't you use: __GNUC__ >=5 || (__GNUC__ == 4 && __GNUC_MINOR__ >= 9) instead for checking GCC version?