public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@Synopsys.COM>
To: dje@watson.ibm.com (David Edelsohn)
Cc: Marc.Espie@liafa1.liafa.jussieu.fr, john@feith.com, egcs@egcs.cygnus.com
Subject: Re: ridiculous amounts of padding
Date: Sun, 31 Jan 1999 23:58:00 -0000	[thread overview]
Message-ID: <199901142245.OAA00064@atrus.synopsys.com> (raw)
In-Reply-To: <9901142233.AA58388@marc.watson.ibm.com>

> 	I think that EGCS needs to start looking more carefully at code
> efficiency.  So far there has been a lot of work adding new optimization
> passes and then squashing bugs before a release without the actual benefit
> and efficiency of the resulting code compared to previous versions of GCC
> as a release engineering quality assurance requirement.
> 
> 	Maybe this just isn't sexy or we do not have enough volunteers
> looking at this or the focus on c-torture results is ignoring performance
> results. 

This is, I think, in part due to the fact that we distribute a test suite
which lots of people run, but we don't have a systematic set of
performance benchmarks.  If someone published, say, a full set of Spec95
numbers based on each week's snapshot, I'm sure we'd start seeing
attention paid to such matters.




  reply	other threads:[~1999-01-31 23:58 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-31 23:58 John Wehle
1999-01-31 23:58 ` Marc Espie
1999-01-31 23:58   ` David Edelsohn
1999-01-31 23:58     ` Joe Buck [this message]
1999-01-31 23:58       ` Gabriel Dos Reis
1999-01-31 23:58         ` Joe Buck
1999-01-31 23:58           ` Jeffrey A Law
1999-01-31 23:58   ` Jeffrey A Law
1999-01-30 16:35     ` Marc Lehmann
1999-01-31 20:05       ` Jeffrey A Law
1999-02-01  8:07         ` Marc Lehmann
1999-02-28 22:53           ` Marc Lehmann
1999-01-31 23:58       ` Marc Lehmann
1999-01-31 23:58   ` Joe Buck
1999-01-31 23:58     ` Marc Espie
  -- strict thread matches above, loose matches on Subject: below --
1999-02-01 17:28 N8TM
1999-02-28 22:53 ` N8TM
1999-01-31 23:58 John Wehle
1999-01-31 23:58 Zack Weinberg
1999-01-31 23:58 ` Alfred Perlstein
1999-01-31 23:58 ` Joern Rennecke
1999-01-31 23:58   ` Jeffrey A Law
1999-01-31 23:58     ` Peter Barada
1999-01-31 23:58       ` Marc Espie
1999-01-31 23:58       ` Nick Ing-Simmons
1999-01-31 23:58         ` Joern Rennecke
1999-01-31 23:58           ` John Vickers
1999-01-31 23:58             ` Joern Rennecke
1999-01-31 23:58       ` Zack Weinberg
1999-01-31 23:58         ` Jeffrey A Law
1999-01-31 23:58           ` Zack Weinberg
1999-01-31 23:58             ` Jeffrey A Law
1999-01-31 23:58     ` Joern Rennecke
1999-01-31 23:58       ` Jeffrey A Law
1999-01-31 23:58 N8TM
1999-01-31 23:58 ` Zack Weinberg
1999-01-31 23:58   ` Jeffrey A Law

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=199901142245.OAA00064@atrus.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=Marc.Espie@liafa1.liafa.jussieu.fr \
    --cc=dje@watson.ibm.com \
    --cc=egcs@egcs.cygnus.com \
    --cc=john@feith.com \
    /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).