public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56746] [4.8 regression] increased memory usage when compiling C++
Date: Fri, 29 Mar 2013 18:44:00 -0000 [thread overview]
Message-ID: <bug-56746-4-547ZhMg8UK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56746-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56746
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org
--- Comment #8 from Jason Merrill <jason at gcc dot gnu.org> 2013-03-29 18:43:55 UTC ---
(In reply to comment #7)
> So it seems the macro expansion tracking is what's causing a lot of extra
> memory usage here.
OK, that makes sense, as the compiler is keeping more information around in
order to give better diagnostic context with macros.
next prev parent reply other threads:[~2013-03-29 18:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 18:07 [Bug c++/56746] New: 4.8 regression: " mathias at gaunard dot com
2013-03-27 9:50 ` [Bug c++/56746] [4.8 regression] " rguenth at gcc dot gnu.org
2013-03-27 11:04 ` mathias at gaunard dot com
2013-03-27 11:09 ` paolo.carlini at oracle dot com
2013-03-27 11:12 ` redi at gcc dot gnu.org
2013-03-27 16:41 ` mathias at gaunard dot com
2013-03-28 9:51 ` rguenth at gcc dot gnu.org
2013-03-28 10:39 ` mathias at gaunard dot com
2013-03-29 18:44 ` jason at gcc dot gnu.org [this message]
2013-04-26 18:10 ` jakub at gcc dot gnu.org
2013-05-31 11:00 ` jakub at gcc dot gnu.org
2013-06-13 15:49 ` mathias at gaunard dot com
2013-06-13 15:54 ` mathias at gaunard dot com
2013-10-05 9:29 ` ofv at wanadoo dot es
2013-10-16 9:51 ` jakub at gcc dot gnu.org
2014-05-22 9:07 ` rguenth at gcc dot gnu.org
2014-12-19 13:34 ` jakub at gcc dot gnu.org
2015-06-23 8:41 ` rguenth at gcc dot gnu.org
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-56746-4-547ZhMg8UK@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).