public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Steven Bosscher <stevenb@suse.de>,  gcc@gcc.gnu.org
Subject: Re: GCC 3.5 Status (2004-08-29)
Date: Mon, 30 Aug 2004 01:53:00 -0000	[thread overview]
Message-ID: <41327EE6.4010300@codesourcery.com> (raw)
In-Reply-To: <1093827433.29639.20.camel@dberlin.org>

Daniel Berlin wrote:

>>> I am confident that there
>>>are alternatives that, while perhaps less comprehensive, get enough of
>>>the common cases to achieve most of the benefits.
>>>      
>>>
>>What is your confidence based on?  What common cases?  Did Dan tell you
>>about the issues that he's fighting?  No "less comprehensive" solution
>>exists that will not run into the exact same problems.
>>
>>    
>>
>
>I didn't tell him about the issues i'm fighting, so he's probably just
>stating the typical result, ie "It takes less time to get the common
>cases than it does to get all the cases".
>
>Of course, the issues i'm dealing with are things that were punted on
>earlier in the design of tree-ssa, because they were either hard to get
>right, we didn't have time then, etc.
>
>Let me give an example issue from an email i sent to diego and richard,
>as a motivating example.
>  
>
Yes, there's some design work to be done.  That's why I believed your 
estimate about how long it will take, and why parallelizing the work 
will only help so much: you still have to agree on a design up front.

I still think there are likely to be expedient hacks that get you a lot 
of the win.  Note that the RTL optimizers didn't know about fields at 
all until recently (3.4?).  So, perhaps we can deal with the 
compile-time issue by accepting somewhat inferior generated code.  
Perhaps you can wait until SRA runs, and then just DTRT for objects that 
get SRA'd.  I don't have the answer; I'm just saying that there's likely 
to be one out there somewhere.  GCC got by for years with exactly this 
kind of solution, and actually managed to generate relatively decent 
code relatively often.

-- 
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com

  reply	other threads:[~2004-08-30  1:12 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-29 23:49 Mark Mitchell
2004-08-30  0:03 ` Andrew Pinski
2004-08-30  0:33   ` Mark Mitchell
2004-08-30  0:53     ` Daniel Berlin
2004-08-30  0:25 ` Steven Bosscher
2004-08-30  0:48   ` Mark Mitchell
2004-08-30  0:57     ` Steven Bosscher
2004-08-30  1:04       ` Mark Mitchell
2004-08-30  1:12         ` Andrew Pinski
2004-08-30  1:29           ` Mark Mitchell
2004-08-30 10:11           ` Joseph S. Myers
2004-08-30  2:46         ` Giovanni Bajo
2004-08-30  3:09           ` Matt Austern
2004-08-30 13:51             ` Speeding up C++ at -O0 (Was: GCC 3.5 Status (2004-08-29)) Giovanni Bajo
2004-08-30 18:02             ` GCC 3.5 Status (2004-08-29) Joe Buck
2004-08-30  3:32           ` Gabriel Dos Reis
2004-08-30  4:11             ` Mark Mitchell
2004-08-30  4:17               ` Gabriel Dos Reis
2004-08-30  4:43                 ` Mark Mitchell
2004-08-30  5:09                   ` Gabriel Dos Reis
2004-08-30  5:27                     ` Mark Mitchell
2004-08-30  5:30                       ` Gabriel Dos Reis
2004-08-30  6:57                         ` Mark Mitchell
2004-08-30  9:24           ` Steven Bosscher
2004-08-30 10:13             ` Giovanni Bajo
2004-08-30 10:26               ` Steven Bosscher
2004-08-30 16:34                 ` Jan Hubicka
2004-08-30 11:02           ` Paolo Bonzini
2004-08-30 10:03         ` Steven Bosscher
2004-08-30 15:11           ` Mark Mitchell
2004-08-30 15:21           ` Jan Hubicka
2004-08-30 17:46           ` Jeffrey A Law
2004-08-30  1:09       ` Daniel Berlin
2004-08-30  1:53         ` Mark Mitchell [this message]
2004-08-30  7:34           ` Steven Bosscher
2004-08-30  8:15             ` Mark Mitchell
2004-08-30 14:16               ` Daniel Berlin
2004-08-30 15:10                 ` Mark Mitchell
2004-08-30  3:03 ` Daniel Berlin
2004-08-30  3:20   ` Mark Mitchell
2004-08-31 17:35   ` Joseph S. Myers
2004-08-30 10:50 ` Dorit Naishlos
2004-08-30 15:12   ` Mark Mitchell
2004-08-30 14:26 ` Jan Hubicka
2004-08-30 15:03   ` Mark Mitchell
2004-08-30 15:05     ` Jan Hubicka
2004-08-30 17:08 ` Diego Novillo
2004-08-31  3:25 ` Devang Patel
2004-08-30  0:59 Richard Kenner
2004-08-30  4:33 Nathanael Nerode
2004-08-30 10:17 Richard Kenner
2004-08-30 14:48 ` Mark Mitchell
2004-08-30 18:08   ` Mike Stump
2004-08-30 10:44 Richard Kenner
2004-08-30 11:27 ` Laurent GUERBY
2004-08-30 13:05   ` Jakub Jelinek
2004-08-30 18:28     ` Laurent GUERBY
2004-08-30 20:04       ` Jakub Jelinek
2004-08-30 20:25         ` Laurent GUERBY
2004-08-31  5:27           ` Eric Botcazou
2004-08-31  9:42           ` Arnaud Charlet
2004-08-30 20:14       ` Florian Weimer

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=41327EE6.4010300@codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=dberlin@dberlin.org \
    --cc=gcc@gcc.gnu.org \
    --cc=stevenb@suse.de \
    /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).