public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/31976] [4.3 Regression] ICE in ssa_operand_alloc, at tree-ssa-operands.c:487 with -O3
Date: Wed, 07 Nov 2007 15:06:00 -0000 [thread overview]
Message-ID: <20071107150558.19869.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31976-12387@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from rguenther at suse dot de 2007-11-07 15:05 -------
Subject: Re: [4.3 Regression] ICE in
ssa_operand_alloc, at tree-ssa-operands.c:487 with -O3
On Wed, 7 Nov 2007, dnovillo at google dot com wrote:
> Subject: Re: [4.3 Regression] ICE in ssa_operand_alloc, at
> tree-ssa-operands.c:487 with -O3
>
> On 7 Nov 2007 13:52:29 -0000, amacleod at redhat dot com
> <gcc-bugzilla@gcc.gnu.org> wrote:
>
> > There is also an issue with partitioning, but it would then hide what I
> > think is an important issue.
> >
> > Partitioning's problem is that it counts the number of items in the
> > alias set and just uses that. There is only one entry for an entire SFT
> > list, so it misses the other 819 in this particular list. The difficulty
> > is determining how many of those SFTs are actually going to be
> > relevant. Ideally, partitioning would share code with VOP processing so
> > it can see exactly how many VOPs would be generated by each MEM.
>
> Agreed. The partitioner heuristics got severely skewed when we
> switched alias sets to only contain the first SFT in the pointed-to
> structure. But that should be a relatively simple fix.
It actually contains all pointed-to SFTs. But yes, we should be able
to fix this by conservatively counting VOPs (that is, rather
overestimate). I plan to look at the heuristics as soon as we settled
on a fix for the wrong-code PR33870.
Richard.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31976
next prev parent reply other threads:[~2007-11-07 15:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 15:22 [Bug tree-optimization/31976] New: " tbm at cyrius dot com
2007-05-18 13:58 ` [Bug tree-optimization/31976] " tbm at cyrius dot com
2007-05-18 20:32 ` tbm at cyrius dot com
2007-06-10 2:37 ` pinskia at gcc dot gnu dot org
2007-06-10 2:57 ` pinskia at gcc dot gnu dot org
2007-06-29 18:30 ` mmitchel at gcc dot gnu dot org
2007-08-14 8:44 ` belyshev at depni dot sinp dot msu dot ru
2007-08-14 8:53 ` belyshev at depni dot sinp dot msu dot ru
2007-10-17 10:49 ` pranav dot bhandarkar at gmail dot com
2007-10-17 10:50 ` pranav dot bhandarkar at gmail dot com
2007-11-05 22:32 ` rguenth at gcc dot gnu dot org
2007-11-06 15:28 ` amacleod at redhat dot com
2007-11-06 21:36 ` rguenther at suse dot de
2007-11-07 13:52 ` amacleod at redhat dot com
2007-11-07 13:58 ` dnovillo at google dot com
2007-11-07 15:06 ` rguenther at suse dot de [this message]
2007-11-07 15:14 ` dnovillo at google dot com
2008-01-02 13:00 ` rguenth at gcc dot gnu dot 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=20071107150558.19869.qmail@sourceware.org \
--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).