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/113808] [14 Regression] FAIL: libgomp.fortran/non-rectangular-loop-1.f90 since r14-8768
Date: Wed, 07 Feb 2024 14:25:43 +0000	[thread overview]
Message-ID: <bug-113808-4-QqGSGgzJU5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113808-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
It's surely a bug in the vectorizer early exit handling.  I just don't know
what exactly is wrong right now ;)

  parent reply	other threads:[~2024-02-07 14:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 12:47 [Bug tree-optimization/113808] New: [14 Regression] FAIL: libgomp.fortran/non-rectangular-loop-1.f90 rguenth at gcc dot gnu.org
2024-02-07 13:28 ` [Bug tree-optimization/113808] " rguenth at gcc dot gnu.org
2024-02-07 13:37 ` tnfchris at gcc dot gnu.org
2024-02-07 13:39 ` [Bug tree-optimization/113808] [14 Regression] FAIL: libgomp.fortran/non-rectangular-loop-1.f90 since r14-8768 jakub at gcc dot gnu.org
2024-02-07 13:48 ` rguenth at gcc dot gnu.org
2024-02-07 13:53 ` rguenth at gcc dot gnu.org
2024-02-07 14:09 ` rguenth at gcc dot gnu.org
2024-02-07 14:20 ` jakub at gcc dot gnu.org
2024-02-07 14:20 ` jakub at gcc dot gnu.org
2024-02-07 14:25 ` rguenth at gcc dot gnu.org [this message]
2024-02-08  4:28 ` tnfchris at gcc dot gnu.org
2024-02-08 10:44 ` cvs-commit at gcc dot gnu.org
2024-02-08 10:45 ` tnfchris at gcc dot gnu.org
2024-02-08 11:11 ` 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-113808-4-QqGSGgzJU5@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).