public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "avieira at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/100981] ICE in info_for_reduction, at tree-vect-loop.c:4897 Date: Wed, 09 Jun 2021 14:23:37 +0000 [thread overview] Message-ID: <bug-100981-4-JXrikaoa8A@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100981-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100981 --- Comment #6 from avieira at gcc dot gnu.org --- FYI Tamar asked me to make sure the instructions were being generated. I checked and they were, but not being used as it decides to inline MAIN__ and inlining seems to break (as in not apply/missed oppurtunity) the complex optimization. So for this specific test I'd use -fno-inline, it executes the fcmla instructions that way and it runs fine.
next prev parent reply other threads:[~2021-06-09 14:23 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-09 3:26 [Bug target/100981] New: " asolokha at gmx dot com 2021-06-09 6:48 ` [Bug tree-optimization/100981] " rguenth at gcc dot gnu.org 2021-06-09 7:33 ` rguenth at gcc dot gnu.org 2021-06-09 7:34 ` rguenth at gcc dot gnu.org 2021-06-09 7:55 ` rguenth at gcc dot gnu.org 2021-06-09 12:34 ` avieira at gcc dot gnu.org 2021-06-09 14:23 ` avieira at gcc dot gnu.org [this message] 2021-06-09 14:35 ` cvs-commit at gcc dot gnu.org 2021-06-09 14:36 ` [Bug tree-optimization/100981] [11 Regression] " rguenth at gcc dot gnu.org 2021-06-10 7:32 ` cvs-commit at gcc dot gnu.org 2021-06-16 13:12 ` cvs-commit at gcc dot gnu.org 2021-06-16 13:13 ` 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-100981-4-JXrikaoa8A@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).