public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rdapp at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100756] vect: Superfluous epilog created on s390x
Date: Fri, 25 Mar 2022 09:45:25 +0000 [thread overview]
Message-ID: <bug-100756-4-4TjTxo47wU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100756-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100756
--- Comment #2 from rdapp at linux dot ibm.com ---
I did not get back to this until now. The patch works, of course and a
testsuite run looks good so far. I assume we're too late in the cycle to still
get this in, right?
next prev parent reply other threads:[~2022-03-25 9:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 16:22 [Bug tree-optimization/100756] New: " rdapp at linux dot ibm.com
2021-05-26 7:39 ` [Bug tree-optimization/100756] " rguenth at gcc dot gnu.org
2022-03-25 9:45 ` rdapp at linux dot ibm.com [this message]
2022-03-25 9:53 ` rguenth at gcc dot gnu.org
2022-10-20 12:04 ` rdapp at gcc dot gnu.org
2022-10-21 12:21 ` [Bug tree-optimization/100756] [12/13 Regression] " rguenth at gcc dot gnu.org
2022-10-25 8:03 ` cvs-commit at gcc dot gnu.org
2022-10-25 8:03 ` [Bug tree-optimization/100756] [12 " rguenth at gcc dot gnu.org
2022-10-25 8:03 ` rguenth at gcc dot gnu.org
2023-02-01 9:31 ` rguenth at gcc dot gnu.org
2023-02-01 9:59 ` rdapp at gcc dot gnu.org
2023-05-08 12:22 ` rguenth 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-100756-4-4TjTxo47wU@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).