[Bug c++/81239] std::__cxx11::string& visible in gcc warning output

2019-01-02 Thread jg at jguk dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81239 --- Comment #10 from Jonny Grant --- Would you agree "abi11" would not have suffered the "cxx11" ambiguity? Hope this can be avoided next time another ABI needs to be added to accommodate a change in language behaviour.

[Bug c++/81239] std::__cxx11::string& visible in gcc warning output

2019-01-02 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81239 --- Comment #9 from Jonathan Wakely --- It's the ABI that meets the requirements of the C++11 standard, but that doesn't mean it's enabled by the -std=c++11 flag. The -std flags never change ABI, irrespective of the names used for attributes and

[Bug c++/81239] std::__cxx11::string& visible in gcc warning output

2018-12-29 Thread jg at jguk dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81239 --- Comment #8 from Jonny Grant --- (In reply to Jonathan Wakely from comment #7) > (In reply to Jonny Grant from comment #5) > > (In reply to Jonathan Wakely from comment #4) > > > I fixed the std::__cxx11::string case on trunk, the output is no

[Bug c++/81239] std::__cxx11::string& visible in gcc warning output

2018-12-17 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81239 --- Comment #7 from Jonathan Wakely --- (In reply to Jonny Grant from comment #5) > (In reply to Jonathan Wakely from comment #4) > > I fixed the std::__cxx11::string case on trunk, the output is now: > > Great! > > I wonder how this looks now

[Bug c++/81239] std::__cxx11::string& visible in gcc warning output

2018-12-17 Thread jg at jguk dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81239 --- Comment #6 from Jonny Grant --- > I imagine you may have found out that this goes away if the "const" is > removed. So it becomes > void test_params(string & mystr1, string & out_str) To add, by this I mean the std:: namespace is visible, p

[Bug c++/81239] std::__cxx11::string& visible in gcc warning output

2018-12-17 Thread jg at jguk dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81239 --- Comment #5 from Jonny Grant --- (In reply to Jonathan Wakely from comment #4) > I fixed the std::__cxx11::string case on trunk, the output is now: Great! I wonder how this looks now with -std=c++14or -std=c++17 (not sure why I still

[Bug c++/81239] std::__cxx11::string& visible in gcc warning output

2018-12-17 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81239 Jonathan Wakely changed: What|Removed |Added Last reconfirmed|2017-06-28 00:00:00 |2018-12-17 --- Comment #4 from Jonatha

[Bug c++/81239] std::__cxx11::string& visible in gcc warning output

2018-08-02 Thread jg at jguk dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81239 --- Comment #3 from Jonny Grant --- (In reply to Jonny Grant from comment #2) > Created attachment 44492 [details] > Better test case wrong ticket. please ignore

[Bug c++/81239] std::__cxx11::string& visible in gcc warning output

2018-08-02 Thread jg at jguk dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81239 --- Comment #2 from Jonny Grant --- Created attachment 44492 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44492&action=edit Better test case

[Bug c++/81239] std::__cxx11::string& visible in gcc warning output

2017-06-28 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81239 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|