public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108970] [13 Regression] ICE in vect_do_peeling, at tree-vect-loop-manip.cc:2971, or ICE in dump_printf_loc, at dumpfile.cc:1359 Date: Wed, 01 Mar 2023 07:42:31 +0000 [thread overview] Message-ID: <bug-108970-4-OR2Xr993Tw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108970-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108970 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Ever confirmed|0 |1 Last reconfirmed| |2023-03-01 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. I will have a look. Without -fsave-optimization-record it ICEs with during GIMPLE pass: vect t.c: In function ‘foo’: t.c:9:1: internal compiler error: in dump_printf_loc, at dumpfile.cc:1359 9 | foo (void) | ^~~ 0xf7d9c2 dump_printf_loc(dump_metadata_t const&, dump_user_location_t const&, char const*, ...) /space/rguenther/src/gcc/gcc/dumpfile.cc:1359 0x194d5ee vect_do_peeling(_loop_vec_info*, tree_node*, tree_node*, tree_node**, tree_node**, tree_node**, int, bool, bool, tree_node**) /space/rguenther/src/gcc/gcc/tree-vect-loop-manip.cc:2969
next prev parent reply other threads:[~2023-03-01 7:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-28 16:47 [Bug tree-optimization/108970] New: " asolokha at gmx dot com 2023-02-28 16:50 ` [Bug tree-optimization/108970] " pinskia at gcc dot gnu.org 2023-03-01 7:42 ` rguenth at gcc dot gnu.org [this message] 2023-03-01 9:10 ` cvs-commit at gcc dot gnu.org 2023-03-01 9:12 ` 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-108970-4-OR2Xr993Tw@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: linkBe 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).