public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zadeck at naturalbridge dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/35805] [ira] error in start_allocno_priorities, at ira-color.c:1806
Date: Fri, 02 Jan 2009 18:56:00 -0000	[thread overview]
Message-ID: <20090102185443.6028.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35805-14137@http.gcc.gnu.org/bugzilla/>



------- Comment #14 from zadeck at naturalbridge dot com  2009-01-02 18:54 -------
Subject: Re:  [ira] error in start_allocno_priorities,
 at ira-color.c:1806

Steven Bosscher wrote:
> On Fri, Jan 2, 2009 at 7:37 PM, Paolo Bonzini <bonzini@gnu.org> wrote:
>   
>>>> At this point, if your patch costs say 0.3%, and removing all traces
>>>> DF_LR_RUN_DCE (instead scheduling a dozen more pass_fast_rtl_dce in
>>>> passes.c) costs 0.5%, I'd rather see the latter, at least it's easier to
>>>> look for opportunities to remove some useless DCE.
>>>>         
>> I'll try to do this for 4.5.
>>     
>
> It might be more worthwhile to just "fix" IRA to use DF_LIVE (which
> Vlad should have done in the first place). Then we wouldn't need
> Kenny's patch and DF_LR_RUN_DCE would still be essentially free.
>
> Gr.
> Steven
There is the issue of correctness vs rot.   I actually think that one of
the reasons that flow was so bad was that people went down this long
slippery slope of well it is good enough here ... and we really can get
away with it not being right here ... and after a while, all you have is
garbage.

The problem with this game is that it is not maintainable.   Those kinds
of decisions tend to get forgotten and lost as the personnel supporting
the compiler changes.    Even if it is a fractional percentage slower,
the fact that you do not have to reason about it as the compiler evolves
is actually quite important.  

Thus, I plan to both fix this bug and add another one for vlad to fix
the sets that he uses. 

Kenny


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35805


  parent reply	other threads:[~2009-01-02 18:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 16:47 [Bug tree-optimization/35805] New: " mstein dot lists at googlemail dot com
2008-04-02 18:35 ` [Bug tree-optimization/35805] " vmakarov at redhat dot com
2008-12-29 23:28 ` reichelt at gcc dot gnu dot org
2008-12-29 23:42 ` zadeck at naturalbridge dot com
2009-01-02  0:40 ` zadeck at naturalbridge dot com
2009-01-02  8:18 ` bonzini at gnu dot org
2009-01-02 14:11 ` zadeck at naturalbridge dot com
2009-01-02 14:28 ` bonzini at gnu dot org
2009-01-02 15:22 ` zadeck at naturalbridge dot com
2009-01-02 15:36 ` zadeck at naturalbridge dot com
2009-01-02 16:34 ` bonzini at gnu dot org
2009-01-02 18:23 ` zadeck at naturalbridge dot com
2009-01-02 18:39 ` bonzini at gnu dot org
2009-01-02 18:47 ` stevenb dot gcc at gmail dot com
2009-01-02 18:56 ` zadeck at naturalbridge dot com [this message]
2009-01-03  0:34 ` zadeck at gcc dot gnu dot org
2009-01-03  0:37 ` zadeck at naturalbridge dot com
2009-01-03  1:08 ` zadeck at naturalbridge dot com
2009-01-04 18:23 ` hjl dot tools at gmail dot com

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=20090102185443.6028.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).