public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98535] [11 Regression] ICE in operands_scanner::get_expr_operands(tree_node**, int) building 538.imagick_r
Date: Tue, 19 Jan 2021 12:13:04 +0000 [thread overview]
Message-ID: <bug-98535-4-WzwpPg0SnX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98535-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98535
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|rguenth at gcc dot gnu.org |rsandifo at gcc dot gnu.org
--- Comment #9 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
I think the problem is in the way that noutputs_bound is used.
If we force limit = nvectors to suppress the (attempted) DCE,
we get the correct output.
In other words, the optimisation is trying to make sure
we only generate the bare mininum vectors needed on each
iteration. But in this case it's generating the wrong ones.
Perhaps it would be easier to get rid of that and do something
similar to the i&1 handling inside the loop.
next prev parent reply other threads:[~2021-01-19 12:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 15:43 [Bug tree-optimization/98535] New: " ktkachov at gcc dot gnu.org
2021-01-05 15:43 ` [Bug tree-optimization/98535] " ktkachov at gcc dot gnu.org
2021-01-05 17:01 ` ktkachov at gcc dot gnu.org
2021-01-05 18:54 ` ktkachov at gcc dot gnu.org
2021-01-05 20:18 ` marxin at gcc dot gnu.org
2021-01-06 8:49 ` rguenth at gcc dot gnu.org
2021-01-19 10:04 ` rguenth at gcc dot gnu.org
2021-01-19 10:35 ` rguenth at gcc dot gnu.org
2021-01-19 10:38 ` rguenth at gcc dot gnu.org
2021-01-19 11:19 ` rsandifo at gcc dot gnu.org
2021-01-19 12:13 ` rsandifo at gcc dot gnu.org [this message]
2021-01-20 13:17 ` cvs-commit at gcc dot gnu.org
2021-01-20 13:26 ` rsandifo at gcc dot gnu.org
2021-01-22 9:13 ` cvs-commit at gcc dot gnu.org
2021-01-22 9:19 ` rsandifo 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-98535-4-WzwpPg0SnX@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).