public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/36294] gcc exited and told me to report a bug (details follow)
Date: Tue, 20 Feb 2024 12:55:13 +0000	[thread overview]
Message-ID: <bug-36294-4-OwIneOiOnP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-36294-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36294

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
GCC 14 takes around 380MB and 14s for me.  Nothing sticks out in particular
with respect to profile nor memory.  The GCC 4.2.1 binary I have around uses
482MB and 18s with PTA using 46% of the compile-time.

I can't say 380MB is much better than 482MB but at least we didn't regress
and it's now 15 years later and we don't consider 380MB excessive.

I'd still say fixed now, the testcase itself isn't particularly interesting.

  parent reply	other threads:[~2024-02-20 12:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-36294-4@http.gcc.gnu.org/bugzilla/>
2012-02-02 18:45 ` pinskia at gcc dot gnu.org
2024-02-20 12:55 ` rguenth at gcc dot gnu.org [this message]
2008-05-22  0:24 [Bug c/36294] New: " paulbeard at gmail dot com
2008-05-22  3:06 ` [Bug middle-end/36294] " paulbeard at gmail dot com
2008-05-22 10:18 ` rguenth at gcc dot gnu dot org
2008-05-22 14:32 ` paulbeard at gmail dot com
2008-05-22 20:02 ` pinskia at gcc dot gnu dot org
2008-05-22 23:19 ` paulbeard at gmail dot com
2008-05-24 20:17 ` paulbeard 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=bug-36294-4-OwIneOiOnP@http.gcc.gnu.org/bugzilla/ \
    --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).