public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110544] [14 regression] gcc.dg/vect/pr71264.c ICEs after r14-2150
Date: Wed, 05 Jul 2023 14:41:16 +0000	[thread overview]
Message-ID: <bug-110544-4-7iyqbDVKQW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110544-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from seurer at gcc dot gnu.org ---
I just tried it with current trunk and I no longer see an ICE either. 
However...

g:429905d809bbf2398bf666d65322b87ac7381e43, r14-2320-g429905d809bbf2
make  -k check-gcc RUNTESTFLAGS="vect.exp=gcc.dg/vect/pr71264.c"
FAIL: gcc.dg/vect/pr71264.c scan-tree-dump vect "vectorized 1 loops in
function"
FAIL: gcc.dg/vect/pr71264.c -flto -ffat-lto-objects  scan-tree-dump vect
"vectorized 1 loops in function"
# of expected passes            2
# of unexpected failures        2

configure --enable-languages=c,fortran,c++ --enable-secureplt
--with-cpu=power10 --disable-bootstrap --disable-multilib

  parent reply	other threads:[~2023-07-05 14:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 13:47 [Bug tree-optimization/110544] New: " seurer at gcc dot gnu.org
2023-07-05  7:00 ` [Bug tree-optimization/110544] " rguenth at gcc dot gnu.org
2023-07-05  7:17 ` rguenth at gcc dot gnu.org
2023-07-05 14:41 ` seurer at gcc dot gnu.org [this message]
2023-07-06  6:55 ` cvs-commit at gcc dot gnu.org
2023-07-06  6:55 ` 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-110544-4-7iyqbDVKQW@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).