From: Tony Bryant <brd@paradise.net.nz>
To: gcc@gcc.gnu.org
Subject: C++ slow/swappy problem solved
Date: Mon, 14 Oct 2002 02:08:00 -0000 [thread overview]
Message-ID: <200210141454.35617.brd@paradise.net.nz> (raw)
I've reduced the 160Mb compile down to
this fragment:
-------------------------------------
class x
{
public:
unsigned long mem[1024*1024*10];
x();
};
class y : public x
{
public:
y();
};
----------------------------------------
Some digging show that "record_subobject_offset" in class.c is being
called for EVERY item in x::mem
I now have enough info for a workaround, and I've put an entry in gnatsweb -
Do with it what you will....
BTW- the allocated offset information isn't showing up in -fmem-report....
next reply other threads:[~2002-10-14 1:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 2:08 Tony Bryant [this message]
2002-10-15 15:27 ` Gerald Pfeifer
2002-10-15 16:51 ` Richard Henderson
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=200210141454.35617.brd@paradise.net.nz \
--to=brd@paradise.net.nz \
--cc=gcc@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).