public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r12-10243] libstdc++: Fix -Wnonnull warnings during configure Date: Mon, 18 Mar 2024 14:05:16 +0000 (GMT) [thread overview] Message-ID: <20240318140516.648163858430@sourceware.org> (raw) https://gcc.gnu.org/g:93159e1af6e1d42e0e595bdc49da002fc830353c commit r12-10243-g93159e1af6e1d42e0e595bdc49da002fc830353c Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri May 12 12:17:08 2023 +0100 libstdc++: Fix -Wnonnull warnings during configure We should not test for nan by passing it a null pointer, as this can trigger -Wnonnull warnings. Also fix an outdated comment about the default -std mode. libstdc++-v3/ChangeLog: * acinclude.m4 (GLIBCXX_CHECK_C99_TR1): Use a non-null pointer to check for nan, nanf, and nanl. * configure: Regenerate. (cherry picked from commit 6190a74ebee69415b501996821c92f60d892fb81) Diff: --- libstdc++-v3/acinclude.m4 | 8 ++++---- libstdc++-v3/configure | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/libstdc++-v3/acinclude.m4 b/libstdc++-v3/acinclude.m4 index c25e8a70638..3b657f04443 100644 --- a/libstdc++-v3/acinclude.m4 +++ b/libstdc++-v3/acinclude.m4 @@ -1623,7 +1623,7 @@ AC_DEFUN([GLIBCXX_CHECK_C99_TR1], [ AC_LANG_SAVE AC_LANG_CPLUSPLUS - # Use -std=c++98 because the default (-std=gnu++98) leaves __STRICT_ANSI__ + # Use -std=c++98 because -std=gnu++98 leaves __STRICT_ANSI__ # undefined and fake C99 facilities may be spuriously enabled. ac_save_CXXFLAGS="$CXXFLAGS" CXXFLAGS="$CXXFLAGS -std=c++98" @@ -1888,9 +1888,9 @@ AC_DEFUN([GLIBCXX_CHECK_C99_TR1], [ lround(0.0); lroundf(0.0f); lroundl(0.0l); - nan(0); - nanf(0); - nanl(0); + nan(""); + nanf(""); + nanl(""); nearbyint(0.0); nearbyintf(0.0f); nearbyintl(0.0l); diff --git a/libstdc++-v3/configure b/libstdc++-v3/configure index 67cae65c533..926d91b076b 100755 --- a/libstdc++-v3/configure +++ b/libstdc++-v3/configure @@ -19695,7 +19695,7 @@ ac_link='$CXX -o conftest$ac_exeext $CXXFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ex ac_compiler_gnu=$ac_cv_cxx_compiler_gnu - # Use -std=c++98 because the default (-std=gnu++98) leaves __STRICT_ANSI__ + # Use -std=c++98 because -std=gnu++98 leaves __STRICT_ANSI__ # undefined and fake C99 facilities may be spuriously enabled. ac_save_CXXFLAGS="$CXXFLAGS" CXXFLAGS="$CXXFLAGS -std=c++98" @@ -20070,9 +20070,9 @@ typedef double_t my_double_t; lround(0.0); lroundf(0.0f); lroundl(0.0l); - nan(0); - nanf(0); - nanl(0); + nan(""); + nanf(""); + nanl(""); nearbyint(0.0); nearbyintf(0.0f); nearbyintl(0.0l);
reply other threads:[~2024-03-18 14:05 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20240318140516.648163858430@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).