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 tree-optimization/99746] [11 Regression] ICE in vect_get_vec_defs_for_operand, at tree-vect-stmts.c:1450
Date: Wed, 24 Mar 2021 16:49:50 +0000 [thread overview]
Message-ID: <bug-99746-4-IqtaY9OuYP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99746-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99746
--- Comment #13 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
(In reply to Arseny Solokha from comment #10)
> (In reply to Tamar Christina from comment #9)
> > I wonder if whatever you're compiling is open source. I'd love to fix some
> > of these cases properly in GCC 12.
>
> These Fortran snippets I've been filing this week are from SCALAPACK 2.0.2
> as found on Netlib[1].
>
> [1] https://www.netlib.org/scalapack
Thanks! This looks like a useful target to improve this with in GCC 12. But am
I missing an option here?:
CC=~/gcc-base/install/bin/gcc \
FC=~/gcc-base/install/bin/gfortran \
CXX=~/gcc-base/install/bin/g++ \
CFLAGS="-march=armv8.3-a -ftree-vectorize -O2" \
CXXFLAGS="-march=armv8.3-a -ftree-vectorize -O2" \
FFLAGS="-march=armv8.3-a -ftree-vectorize -O2" \
cmake .. && make -j
I can't seem to get it to trigger the crash (or even detect the pattern).
next prev parent reply other threads:[~2021-03-24 16:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 6:33 [Bug tree-optimization/99746] New: " asolokha at gmx dot com
2021-03-24 8:34 ` [Bug tree-optimization/99746] " tnfchris at gcc dot gnu.org
2021-03-24 8:38 ` marxin at gcc dot gnu.org
2021-03-24 8:40 ` marxin at gcc dot gnu.org
2021-03-24 8:51 ` tnfchris at gcc dot gnu.org
2021-03-24 9:02 ` marxin at gcc dot gnu.org
2021-03-24 9:05 ` marxin at gcc dot gnu.org
2021-03-24 9:20 ` [Bug tree-optimization/99746] [11 Regression] " rguenth at gcc dot gnu.org
2021-03-24 9:22 ` tnfchris at gcc dot gnu.org
2021-03-24 9:51 ` rguenth at gcc dot gnu.org
2021-03-24 10:03 ` tnfchris at gcc dot gnu.org
2021-03-24 10:15 ` asolokha at gmx dot com
2021-03-24 10:17 ` rguenth at gcc dot gnu.org
2021-03-24 10:42 ` rguenth at gcc dot gnu.org
2021-03-24 16:49 ` tnfchris at gcc dot gnu.org [this message]
2021-03-24 16:50 ` tnfchris at gcc dot gnu.org
2021-03-25 3:56 ` asolokha at gmx dot com
2021-03-25 9:04 ` cvs-commit at gcc dot gnu.org
2021-03-25 9:05 ` rguenth at gcc dot gnu.org
2021-03-26 7:22 ` tnfchris 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-99746-4-IqtaY9OuYP@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).