public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roger at nextmovesoftware dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/106264] [10/11/12/13 Regression] spurious -Wunused-value on a folded frexp, modf, and remquo calls with unused result since r9-1295-g781ff3d80e88d7d0
Date: Wed, 20 Jul 2022 06:07:45 +0000 [thread overview]
Message-ID: <bug-106264-4-xH8R0taEJy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106264-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106264
Roger Sayle <roger at nextmovesoftware dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
Target Milestone|10.5 |13.0
--- Comment #7 from Roger Sayle <roger at nextmovesoftware dot com> ---
This has now been fixed on mainline for GCC 13. Please feel free to reopen
this PR if folks consider this problem serious enough to backport the fix to
the release branches.
next prev parent reply other threads:[~2022-07-20 6:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 21:05 [Bug c/106264] New: spurious -Wunused-value on a folded frexp, modf, and remquo calls with unused result msebor at gcc dot gnu.org
2022-07-11 21:07 ` [Bug c/106264] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org
2022-07-11 21:09 ` pinskia at gcc dot gnu.org
2022-07-11 21:13 ` msebor at gcc dot gnu.org
2022-07-11 21:16 ` pinskia at gcc dot gnu.org
2022-07-12 6:38 ` rguenth at gcc dot gnu.org
2022-07-15 8:34 ` [Bug c/106264] [10/11/12/13 Regression] spurious -Wunused-value on a folded frexp, modf, and remquo calls with unused result since r9-1295-g781ff3d80e88d7d0 marxin at gcc dot gnu.org
2022-07-16 12:59 ` roger at nextmovesoftware dot com
2022-07-19 7:40 ` cvs-commit at gcc dot gnu.org
2022-07-20 6:07 ` roger at nextmovesoftware dot com [this message]
2023-07-18 10:07 ` vincent-gcc at vinc17 dot net
2023-07-18 12:42 ` roger at nextmovesoftware dot com
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=bug-106264-4-xH8R0taEJy@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: link
Be 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).