public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/113731] [14 regression] ICE when building libbsd since r14-8768-g85094e2aa6dba7 Date: Sat, 03 Feb 2024 07:36:07 +0000 [thread overview] Message-ID: <bug-113731-4-qQwGCKGBGk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113731-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113731 Tamar Christina <tnfchris at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2024-02-03 Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |tnfchris at gcc dot gnu.org --- Comment #4 from Tamar Christina <tnfchris at gcc dot gnu.org> --- blah, gsi_move_before (&stmt_gsi, &dest_gsi); when dest_gsi is empty does not move the pointer. It's not mentioned in the description but in the function it eventually calls gsi_insert_before there's a comment /* If CUR is NULL, we link at the end of the sequence (this case happens so it adds it to the end instead of start like you asked. diff --git a/gcc/tree-vect-loop.cc b/gcc/tree-vect-loop.cc index 30b90d99925..e2587315020 100644 --- a/gcc/tree-vect-loop.cc +++ b/gcc/tree-vect-loop.cc @@ -11801,7 +11801,8 @@ move_early_exit_stmts (loop_vec_info loop_vinfo) gimple_stmt_iterator stmt_gsi = gsi_for_stmt (stmt); gsi_move_before (&stmt_gsi, &dest_gsi); - gsi_prev (&dest_gsi); + if (!gsi_end_p (dest_gsi)) + gsi_prev (&dest_gsi); } fixes it. the libarchive, is that also with -march=znver2? and is https://github.com/libarchive/libarchive?
next prev parent reply other threads:[~2024-02-03 7:36 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-02 22:11 [Bug middle-end/113731] New: [14 regression] ICE when building libbsd sjames at gcc dot gnu.org 2024-02-02 22:14 ` [Bug middle-end/113731] " sjames at gcc dot gnu.org 2024-02-02 22:41 ` sjames at gcc dot gnu.org 2024-02-02 22:53 ` sjames at gcc dot gnu.org 2024-02-02 23:08 ` pinskia at gcc dot gnu.org 2024-02-03 7:36 ` tnfchris at gcc dot gnu.org [this message] 2024-02-03 7:50 ` [Bug middle-end/113731] [14 regression] ICE when building libbsd since r14-8768-g85094e2aa6dba7 sjames at gcc dot gnu.org 2024-02-05 15:12 ` [Bug tree-optimization/113731] " tnfchris at gcc dot gnu.org 2024-02-07 3:08 ` sjames at gcc dot gnu.org 2024-02-07 9:03 ` doko at gcc dot gnu.org 2024-02-07 9:08 ` tnfchris at gcc dot gnu.org 2024-02-07 10:00 ` burnus at gcc dot gnu.org 2024-02-07 10:59 ` cvs-commit at gcc dot gnu.org 2024-02-07 11:00 ` tnfchris at gcc dot gnu.org 2024-02-07 21:00 ` sjames 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-113731-4-qQwGCKGBGk@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).