public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109240] Missed fneg/fsub optimization
Date: Sun, 26 Mar 2023 18:44:37 +0000 [thread overview]
Message-ID: <bug-109240-4-K6yWSGT4IS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109240-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109240
Bug 109240 depends on bug 109230, which changed state.
Bug 109230 Summary: [13 Regression] Maybe wrong code for opus package on aarch64 since r13-4122-g1bc7efa948f751
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109230
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
next prev parent reply other threads:[~2023-03-26 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 19:25 [Bug tree-optimization/109240] New: " jakub at gcc dot gnu.org
2023-03-22 7:43 ` [Bug tree-optimization/109240] " rguenth at gcc dot gnu.org
2023-03-22 9:39 ` jakub at gcc dot gnu.org
2023-03-26 18:44 ` jakub at gcc dot gnu.org [this message]
2023-04-18 9:02 ` cvs-commit at gcc dot gnu.org
2023-04-18 9:03 ` jakub at gcc dot gnu.org
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-109240-4-K6yWSGT4IS@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).