public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102087] [12 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: in determine_exit_conditions, at tree-ssa-loop-manip.c:1049 since r12-3136-g3673dcf6d6baeb67
Date: Fri, 24 Sep 2021 17:47:52 +0000	[thread overview]
Message-ID: <bug-102087-4-afAnnrOGaP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102087-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from David Binderman <dcb314 at hotmail dot com> ---
Since this bug depends on the setting of -march,
I tried out all the possible legal settings of that value.

alderlake
amdfam10
during GIMPLE pass: aprefetch
athlon-fx
during GIMPLE pass: aprefetch
athlon64
during GIMPLE pass: aprefetch
athlon64-sse3
during GIMPLE pass: aprefetch
atom
barcelona
during GIMPLE pass: aprefetch
bdver1
during GIMPLE pass: aprefetch
bdver2
during GIMPLE pass: aprefetch
bdver3
during GIMPLE pass: aprefetch
bdver4
during GIMPLE pass: aprefetch
bonnell
broadwell
btver1
during GIMPLE pass: aprefetch
btver2
during GIMPLE pass: aprefetch
cannonlake
cascadelake
cooperlake
core-avx-i
core-avx2
core2
corei7
corei7-avx
eden-x2
during GIMPLE pass: aprefetch
eden-x4
during GIMPLE pass: aprefetch
goldmont
goldmont-plus
haswell
celake-client
icelake-server
ivybridge
k8
during GIMPLE pass: aprefetch
k8-sse3
during GIMPLE pass: aprefetch
knl
knm
nano
during GIMPLE pass: aprefetch
nano-1000
during GIMPLE pass: aprefetch
nano-2000
during GIMPLE pass: aprefetch
nano-3000
during GIMPLE pass: aprefetch
nano-x2
during GIMPLE pass: aprefetch
nano-x4
during GIMPLE pass: aprefetch
native
during GIMPLE pass: aprefetch
nehalem
nocona
opteron
during GIMPLE pass: aprefetch
opteron-sse3
during GIMPLE pass: aprefetch
rocketlake
sandybridge
sapphirerapids
silvermont
skylake
skylake-avx512
slm
tigerlake
tremont
westmere
x86-64
x86-64-v2
x86-64-v3
x86-64-v4
znver1
znver2
znver3

I generated this list with this command:

$ for i in `cat ~/arch.list`; do echo $i; /home/dcb/gcc/results/bin/gcc -c -O3
-march=$i bug760.c 2>&1 | fgrep GIMPLE ; done

  parent reply	other threads:[~2021-09-24 17:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 20:35 [Bug tree-optimization/102087] New: ICE on valid code at -O3 on x86_64-linux-gnu: in determine_exit_conditions, at tree-ssa-loop-manip.c:1049 zhendong.su at inf dot ethz.ch
2021-08-27  7:05 ` [Bug tree-optimization/102087] [12 Regression] " rguenth at gcc dot gnu.org
2021-08-27  7:55 ` [Bug tree-optimization/102087] [12 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: in determine_exit_conditions, at tree-ssa-loop-manip.c:1049 since r12-3136-g3673dcf6d6baeb67 marxin at gcc dot gnu.org
2021-08-27  7:55 ` marxin at gcc dot gnu.org
2021-08-27 10:04 ` guojiufu at gcc dot gnu.org
2021-08-27 12:52 ` hjl.tools at gmail dot com
2021-08-27 12:53 ` hjl.tools at gmail dot com
2021-08-27 13:27 ` guojiufu at gcc dot gnu.org
2021-08-27 14:08 ` guojiufu at gcc dot gnu.org
2021-08-28 20:32 ` dcb314 at hotmail dot com
2021-08-28 20:41 ` dcb314 at hotmail dot com
2021-08-30  3:26 ` guojiufu at gcc dot gnu.org
2021-09-02  9:22 ` pinskia at gcc dot gnu.org
2021-09-22 13:03 ` cvs-commit at gcc dot gnu.org
2021-09-24  7:58 ` dcb314 at hotmail dot com
2021-09-24 12:15 ` rguenth at gcc dot gnu.org
2021-09-24 17:47 ` dcb314 at hotmail dot com [this message]
2021-10-09  5:51 ` guojiufu at gcc dot gnu.org
2021-12-06 15:42 ` asolokha at gmx dot com
2021-12-06 17:43 ` dcb314 at hotmail dot com
2021-12-16  1:47 ` guojiufu at gcc dot gnu.org
2022-01-18  9:27 ` dcb314 at hotmail dot com
2022-01-18  9:37 ` marxin at gcc dot gnu.org
2022-01-19  9:32 ` guojiufu at gcc dot gnu.org
2022-01-24  9:07 ` cvs-commit at gcc dot gnu.org
2022-02-15 12:58 ` 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-102087-4-afAnnrOGaP@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).