public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/78904] zero-extracts are not effective
Date: Fri, 23 Jun 2023 17:47:22 +0000 [thread overview]
Message-ID: <bug-78904-4-DLWawJ5qUG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-78904-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78904
--- Comment #17 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Roger Sayle from comment #16)
> Just to warn people in advance, the test case pr78904-1b.c is expected to
> start FAILing with the commit of
> https://gcc.gnu.org/pipermail/gcc-patches/2023-June/622079.html and is
> scheduled to be resolved 24-48 hours later (over the weekend) by
> https://gcc.gnu.org/pipermail/gcc-patches/2023-June/622078.html
> As explained in
> https://gcc.gnu.org/pipermail/gcc-patches/2023-June/622083.html this is to
> investigate additional tweaks and whether alternate fixes are more
> appropriate.
Thanks for the warning Roger! Much appreciated.
That fix is for x86 only though? Is that really the only target affected?
next prev parent reply other threads:[~2023-06-23 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-78904-4@http.gcc.gnu.org/bugzilla/>
2023-04-19 15:04 ` cvs-commit at gcc dot gnu.org
2023-06-23 8:22 ` roger at nextmovesoftware dot com
2023-06-23 17:47 ` segher at gcc dot gnu.org [this message]
2023-06-24 22:12 ` cvs-commit at gcc dot gnu.org
2023-11-14 17:36 ` cvs-commit at gcc dot gnu.org
2023-11-15 21:22 ` cvs-commit at gcc dot gnu.org
2023-11-16 18:13 ` cvs-commit 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-78904-4-DLWawJ5qUG@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).