public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia@physics.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/10944] alloc_page in ggc-page.c is slow
Date: Fri, 23 May 2003 22:54:00 -0000 [thread overview]
Message-ID: <20030523222940.29619.qmail@sources.redhat.com> (raw)
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10944
------- Additional Comments From pinskia@physics.uc.edu 2003-05-23 22:29 -------
Subject: Re: [Bug other/10944] alloc_page in ggc-page.c is slow
Yes it is spending 90% of the time in alloc_page in that list traversal.
I used Shikari (part of the CHUD tools) on Mac OS X for profiling the
complier
10000 samples ever 1ms (10s in total).
I can find out the backtrace if you want it.
Thanks,
Andrew Pinski
On Friday, May 23, 2003, at 17:52 US/Eastern, zack@gcc.gnu.org wrote:
>
> The code in alloc_page is remarkably stupid, but the linked list
> traversal
> should only occur when trying to allocate an object larger than a
> single
> page, which is believed to happen almost never. Can you please find
> out
> whether it's really spending time in that list, or if some other area
> is
> the cause of the problem?
>
> I'll take responsibility for this bug; I've been meaning to get us
> per-order
> freelists for a long time.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2003-05-23 22:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 22:54 pinskia@physics.uc.edu [this message]
[not found] <20030522192332.10944.pinskia@gcc.gnu.org>
2003-10-12 20:34 ` steven at gcc dot gnu dot org
2003-10-13 14:37 ` steven at gcc dot gnu dot org
2003-11-30 8:38 ` pinskia at gcc dot gnu dot org
2003-12-20 16:31 ` steven at gcc dot gnu dot org
2003-12-23 2:10 ` pinskia at gcc dot gnu dot org
2004-01-17 22:59 ` dhazeghi at yahoo dot com
2004-02-06 1:44 ` pinskia at gcc dot gnu dot org
[not found] <20030522192332.10944.pinskia@physics.uc.edu>
2003-06-01 18:58 ` zack@gcc.gnu.org
-- strict thread matches above, loose matches on Subject: below --
2003-05-23 22:54 pinskia@physics.uc.edu
2003-05-23 22:51 zack@gcc.gnu.org
2003-05-23 22:08 zack@gcc.gnu.org
2003-05-23 20:29 pinskia@physics.uc.edu
2003-05-23 18:14 pinskia@physics.uc.edu
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=20030523222940.29619.qmail@sources.redhat.com \
--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).