public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/112822] [14 regression] ICE: invalid RHS for gimple memory store after r14-5831-gaae723d360ca26
Date: Sat, 02 Dec 2023 18:30:36 +0000	[thread overview]
Message-ID: <bug-112822-4-Jl50IUh5RL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112822-4@http.gcc.gnu.org/bugzilla/>

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

Peter Bergner <bergner at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2023-12-02
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #2 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> >This is a huge C++ program that I have not cut down yet.
> 
> I think it didn't attach because it was too big, maybe compress and attach
> that.

I have a creduce running to minimize it.  Looks like it'll take a while to run.
 I'll attach it when it's done.

I also note Bill's build was configured with --with-cpu=power10, so -O3
-mcpu=power10 are the options required to hit the ICE.

Confirmed.

  parent reply	other threads:[~2023-12-02 18:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-02  2:24 [Bug middle-end/112822] New: " seurer at gcc dot gnu.org
2023-12-02  2:43 ` [Bug middle-end/112822] " pinskia at gcc dot gnu.org
2023-12-02  2:43 ` pinskia at gcc dot gnu.org
2023-12-02 18:30 ` bergner at gcc dot gnu.org [this message]
2023-12-04  3:22 ` bergner at gcc dot gnu.org
2023-12-04  7:01 ` rguenth at gcc dot gnu.org
2023-12-11 15:30 ` jamborm at gcc dot gnu.org
2023-12-11 16:27 ` jamborm at gcc dot gnu.org
2023-12-11 17:53 ` bergner at gcc dot gnu.org
2023-12-11 18:08 ` bergner at gcc dot gnu.org
2023-12-11 19:57 ` bergner at gcc dot gnu.org
2023-12-12 16:56 ` [Bug tree-optimization/112822] " jamborm at gcc dot gnu.org
2023-12-12 20:21 ` cvs-commit at gcc dot gnu.org
2023-12-12 22:46 ` cvs-commit at gcc dot gnu.org
2023-12-12 22:48 ` bergner at gcc dot gnu.org
2023-12-13 14:14 ` 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-112822-4-Jl50IUh5RL@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).