public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jimis at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/53525] Performance regression due to enabling track-macro-expansion
Date: Wed, 30 May 2012 06:06:00 -0000	[thread overview]
Message-ID: <bug-53525-4-Sm60i1I03c@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53525-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53525

--- Comment #7 from jimis <jimis at gmx dot net> 2012-05-30 06:01:23 UTC ---
Now time for the most intrusive and problematic patches. I tried moving all
virt_locs, expanded, expanded_virt_locs to obstacks for allocation. After many
failures to work with obstacks as they are I had to introduce two new
functions, obstack_{mark,release}(), that allow me to continue growing an older
object by pushing and popping a special marker.

Previous patches are included with the following, but I'm submitting it
separately because it's WIP. Even though it is now stable, there is a bad
memory leak that I don't know how to handle since I'm kind of lost in the
macro-expansion code. I'd appreciate suggestions, just search for LEAK or TODO
in my comments. :-p

Please ignore whitespace changes (that are highlighted by emacs so I fix them)
or stylistic changes in parts that I rewrote so many times that lost completely
their initial style.


  parent reply	other threads:[~2012-05-30  6:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30  4:04 [Bug preprocessor/53525] New: " jimis at gmx dot net
2012-05-30  4:24 ` [Bug preprocessor/53525] " jimis at gmx dot net
2012-05-30  4:52 ` jimis at gmx dot net
2012-05-30  5:24 ` jimis at gmx dot net
2012-05-30  5:28 ` jimis at gmx dot net
2012-05-30  5:31 ` jimis at gmx dot net
2012-05-30  6:02 ` jimis at gmx dot net
2012-05-30  6:06 ` jimis at gmx dot net [this message]
2012-05-30  6:10 ` jimis at gmx dot net
2012-05-30  6:24 ` jimis at gmx dot net
2012-05-30  6:25 ` jimis at gmx dot net
2012-05-30  8:38 ` rguenth at gcc dot gnu.org
2012-05-30 16:04 ` jimis at gmx dot net
2012-06-04  4:49 ` jimis at gmx dot net
2012-06-27 22:59 ` jimis at gmx dot net
2012-06-28  9:53 ` rguenth at gcc dot gnu.org
2013-06-13 15:59 ` mathias at gaunard dot com
2013-06-13 20:55 ` manu at gcc dot gnu.org
2013-07-09 12:43 ` mathias at gaunard 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-53525-4-Sm60i1I03c@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).