public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Peter Schmid <schmid@snake.iap.physik.tu-darmstadt.de>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Cc: jason@redhat.com, rth@redhat.com
Subject: Re: GCC 3.1 Prerelease
Date: Sat, 20 Apr 2002 17:57:00 -0000	[thread overview]
Message-ID: <3340000.1019348655@gandalf.codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0204210235010.13395-100000@snake.iap.physik.tu-darmstadt.de>



--On Sunday, April 21, 2002 02:35:57 AM +0200 Peter Schmid 
<schmid@snake.iap.physik.tu-darmstadt.de> wrote:

> In my option PR c++/5504, a gcc 3.0 regression, is a critical bug
> which should be fixed for the upcoming gcc 3.1 release. Otherwise
> blitz will not compile on systems with less than 1.2 GB of virtual
> memory, for this small example. A full blown program will contain much
> more user code requiring even more memory.

This is a compile-time performance regression caused by fixing a
correctness bug.  Correctness trumps; if we can't be both efficient
and correct, we should be correct, within reason.  (And here lots of
programs still compile efficiently; some heavily inlined programs are now
taking more memory to compile.)

I don't quite understand Richard's last note on the topic -- but I
understand his conclusion, which is basically that it's not easy to
fix this problem.  It sounds like maybe if the front end were to
promise that there were no gotos in a particular function, this would
improve things, but I'm not sure.

Jason, Richard, what do you think about this?  The only practical
option, beyond the speedups Richard already implemented, is to
revert Jason's correctness patch at this point.

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com

  reply	other threads:[~2002-04-21  0:28 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.30.0204210235010.13395-100000@snake.iap.physik.tu-da rmstadt.de>
2002-04-20 17:16 ` Peter Schmid
2002-04-20 17:57   ` Mark Mitchell [this message]
2002-04-21 14:16     ` Richard Henderson
2002-04-21 16:54       ` Mark Mitchell
2002-04-23  5:46         ` Jason Merrill
2002-04-23  9:12           ` Mark Mitchell
2002-04-23 14:56 Tom Tromey
  -- strict thread matches above, loose matches on Subject: below --
2002-04-23 13:38 GCC 3.1 prerelease Mark Mitchell
2002-04-23 18:37 ` Kurt Wall
2002-04-23 19:23   ` Phil Edwards
2002-04-24  9:49   ` Mark Mitchell
2002-04-24 11:03     ` Joseph S. Myers
2002-04-24 19:03       ` Kurt Wall
2002-04-23 10:46 GCC 3.1 Prerelease Paolo Carlini
2002-04-23  2:12 Mark Mitchell
2002-04-23  3:53 ` Alan Modra
2002-04-23  4:13   ` Franz Sirl
2002-04-23  4:32     ` Alan Modra
2002-04-23 10:40       ` Franz Sirl
2002-04-23 11:42         ` Richard Henderson
2002-04-23 15:08           ` Franz Sirl
2002-04-23 15:10             ` Richard Henderson
2002-04-24 10:56             ` Jason Merrill
2002-04-24 12:04               ` Franz Sirl
2002-04-24 13:03                 ` Richard Henderson
2002-04-24 13:14                 ` Jason Merrill
2002-04-23 12:22         ` Jason Merrill
2002-04-23  9:08 ` Per Bothner
2002-04-23  9:30   ` Mark Mitchell
2002-04-23 10:12     ` Per Bothner
2002-04-23 13:25       ` Mark Mitchell
2002-04-23 14:52       ` Tom Tromey
2002-04-23 15:02         ` Per Bothner
2002-04-23 16:11           ` Tom Tromey
2002-04-24 10:14             ` Alexandre Petit-Bianco
2002-04-24 10:30               ` Tom Tromey
2002-04-24 10:32                 ` Mark Mitchell
2002-04-23 13:19 ` Richard Henderson
2002-04-23 13:28   ` Mark Mitchell
2002-04-23 13:35     ` Richard Henderson
2002-04-23 13:50       ` Mark Mitchell
2002-04-23 13:52         ` Richard Henderson
2002-04-22 20:00 Billinghurst, David (CRTS)
2002-04-22  4:07 Wolfgang Bangerth
2002-04-22  0:07 Toon Moene
2002-04-20 20:09 John David Anglin
2002-04-20 21:44 ` Mark Mitchell
2002-04-23 12:19   ` John David Anglin
2002-04-21  7:06 ` Toon Moene
2002-04-21 12:57   ` Mark Mitchell
2002-04-21 13:50     ` Franz Sirl
2002-04-22  3:20       ` Gerald Pfeifer
2002-04-22 10:50       ` Franz Sirl
2002-04-22 10:56         ` Mark Mitchell
2002-04-21 20:54     ` John David Anglin
2002-04-22  0:13     ` Richard Henderson
2002-04-22  7:48       ` Mark Mitchell
     [not found] <FAC87D7C874EAB46A847604DA4FD5A640346FC@crtsmail.corp.riotinto.o rg>
2002-04-20 20:05 ` Billinghurst, David (CRTS)
2002-04-20 20:16   ` Mark Mitchell
2002-04-20 13:08 Mark Mitchell
2002-04-20 13:51 ` Stan Shebs
2002-04-20 14:07   ` Mark Mitchell
2002-04-20 16:10   ` Joel Sherrill
2002-04-20 13:56 ` Joseph S. Myers
2002-04-20 13:59   ` Mark Mitchell
2002-04-20 14:36 ` Jakub Jelinek
2002-04-20 17:17   ` Mark Mitchell
2002-04-23  9:49     ` Jakub Jelinek
2002-04-24 10:07       ` Mark Mitchell
2002-04-20 16:35 ` Tom Tromey
2002-04-20 17:28   ` Mark Mitchell
2002-04-20 19:04 ` David S. Miller
2002-04-20 20:08   ` Mark Mitchell
2002-04-20 20:13     ` David S. Miller
2002-04-20 20:18       ` Per Bothner
2002-04-21 11:27         ` Tom Tromey
2002-04-20 20:45       ` Mark Mitchell
2002-04-20 22:09 ` Alan Modra
2002-04-21  3:47 ` Gerald Pfeifer
2002-04-23  8:24   ` Gerald Pfeifer
2002-04-23  9:13     ` Mark Mitchell
2002-04-23  9:36       ` Joe Buck
2002-04-23 14:21         ` Gerald Pfeifer
2002-04-21  8:16 ` Andreas Schwab

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=3340000.1019348655@gandalf.codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=rth@redhat.com \
    --cc=schmid@snake.iap.physik.tu-darmstadt.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).