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/101260] [10/11 Regression] Backport 27381e78925 to GCC 11
Date: Wed, 30 Jun 2021 17:23:35 +0000	[thread overview]
Message-ID: <bug-101260-4-Yc0Lvi2VBR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101260-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101260

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I've reproduced it with -O1 -march=z14 and it started with
r10-7093-g5dc1390b41db5c1765e25fd21dad1a930a015aac
So, I think it is much more likely some RA issue or RTL optimization issue and
the r12-145 change just makes it latent.

  parent reply	other threads:[~2021-06-30 17:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 15:35 [Bug tree-optimization/101260] New: " stefansf at linux dot ibm.com
2021-06-29 23:08 ` [Bug tree-optimization/101260] " jakub at gcc dot gnu.org
2021-06-30  6:33 ` rguenth at gcc dot gnu.org
2021-06-30  7:41 ` stefansf at linux dot ibm.com
2021-06-30  7:58 ` [Bug tree-optimization/101260] [10/11 Regression] " rguenth at gcc dot gnu.org
2021-06-30 14:08 ` stefansf at linux dot ibm.com
2021-06-30 17:23 ` jakub at gcc dot gnu.org [this message]
2021-06-30 19:04 ` stefansf at linux dot ibm.com
2021-07-01 16:58 ` stefansf at linux dot ibm.com
2021-07-06  6:53 ` [Bug rtl-optimization/101260] " rguenth at gcc dot gnu.org
2021-07-19 12:02 ` [Bug rtl-optimization/101260] [10/11/12 " rguenth at gcc dot gnu.org
2021-08-06 13:59 ` stefansf at linux dot ibm.com
2022-01-14 19:24 ` [Bug rtl-optimization/101260] [10/11/12 Regression] regcprop: Determine subreg offset depending on endianness pinskia at gcc dot gnu.org
2022-01-14 19:26 ` pinskia at gcc dot gnu.org
2022-01-14 19:27 ` pinskia at gcc dot gnu.org
2022-01-14 19:32 ` pinskia at gcc dot gnu.org
2022-01-14 19:33 ` pinskia at gcc dot gnu.org
2022-01-14 19:37 ` pinskia at gcc dot gnu.org
2022-02-01 12:35 ` cvs-commit at gcc dot gnu.org
2022-06-09  8:53 ` [Bug rtl-optimization/101260] [10/11 " stefansf at linux dot ibm.com
2022-06-28 10:45 ` jakub at gcc dot gnu.org
2023-07-07 10:40 ` [Bug rtl-optimization/101260] [11 " 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-101260-4-Yc0Lvi2VBR@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).