[Bug libstdc++/89615] FAIL: 17_intro/headers/c++1998/charset.cc (test for excess errors)

2024-09-15 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89615

Jonathan Wakely  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
   Target Milestone|--- |10.0
 Resolution|--- |FIXED

--- Comment #5 from Jonathan Wakely  ---
I think this was fixed by r10-6942-g566f544c3e7e47

[Bug libstdc++/89615] FAIL: 17_intro/headers/c++1998/charset.cc (test for excess errors)

2019-03-11 Thread dave.anglin at bell dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89615

--- Comment #4 from dave.anglin at bell dot net ---
On 2019-03-06 7:26 p.m., redi at gcc dot gnu.org wrote:
> OK, so then maybe something like this:
>
> --- a/libstdc++-v3/include/ext/codecvt_specializations.h
> +++ b/libstdc++-v3/include/ext/codecvt_specializations.h
> @@ -35,6 +35,7 @@
>  #ifndef _EXT_CODECVT_SPECIALIZATIONS_H
>  #define _EXT_CODECVT_SPECIALIZATIONS_H 1
>
> +#if defined __has_include && __has_include()
I had not realized this, but the system has  and it's clearly broken. 
So, the errors
are still there with this change.

[Bug libstdc++/89615] FAIL: 17_intro/headers/c++1998/charset.cc (test for excess errors)

2019-03-06 Thread dave.anglin at bell dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89615

--- Comment #3 from dave.anglin at bell dot net ---
On 2019-03-06 7:26 p.m., redi at gcc dot gnu.org wrote:
> OK, so then maybe something like this:
>
> --- a/libstdc++-v3/include/ext/codecvt_specializations.h
> +++ b/libstdc++-v3/include/ext/codecvt_specializations.h
> @@ -35,6 +35,7 @@
>  #ifndef _EXT_CODECVT_SPECIALIZATIONS_H
>  #define _EXT_CODECVT_SPECIALIZATIONS_H 1
>
> +#if defined __has_include && __has_include()
>  #include 
>  #include 
>  #include 
> @@ -513,3 +514,4 @@ _GLIBCXX_END_NAMESPACE_VERSION
>  } // namespace
>
>  #endif
> +#endif
Added this to my current hpux build.

Dave

[Bug libstdc++/89615] FAIL: 17_intro/headers/c++1998/charset.cc (test for excess errors)

2019-03-06 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89615

--- Comment #2 from Jonathan Wakely  ---
Oh, but it's not failing because of the -finput-charset=ascii option, just
because it includes , and one of the extension ehaders includes
.

OK, so then maybe something like this:

--- a/libstdc++-v3/include/ext/codecvt_specializations.h
+++ b/libstdc++-v3/include/ext/codecvt_specializations.h
@@ -35,6 +35,7 @@
 #ifndef _EXT_CODECVT_SPECIALIZATIONS_H
 #define _EXT_CODECVT_SPECIALIZATIONS_H 1

+#if defined __has_include && __has_include()
 #include 
 #include 
 #include 
@@ -513,3 +514,4 @@ _GLIBCXX_END_NAMESPACE_VERSION
 } // namespace

 #endif
+#endif

[Bug libstdc++/89615] FAIL: 17_intro/headers/c++1998/charset.cc (test for excess errors)

2019-03-06 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89615

Jonathan Wakely  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2019-03-07
 Ever confirmed|0   |1

--- Comment #1 from Jonathan Wakely  ---
We pretty much expected this to fail somewhere. I think we can just skip the
test for this target. Running the test on other targets achieves the aim of
ensuring we have no non-ascii characters in the libstdc++ headers. It doesn't
need to run everywhere.