public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jarkko Hietaniemi <jhi@iki.fi> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/8559: [Tru64] -O3 hogs memory on Perl 5.8.0's toke.c Date: Mon, 03 Feb 2003 21:16:00 -0000 [thread overview] Message-ID: <20030203211601.23002.qmail@sources.redhat.com> (raw) The following reply was made to PR c/8559; it has been noted by GNATS. From: Jarkko Hietaniemi <jhi@iki.fi> To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c/8559: [Tru64] -O3 hogs memory on Perl 5.8.0's toke.c Date: Mon, 3 Feb 2003 23:08:01 +0200 On Mon, Feb 03, 2003 at 08:51:48PM -0000, bangerth@dealii.org wrote: > Synopsis: [Tru64] -O3 hogs memory on Perl 5.8.0's toke.c > > State-Changed-From-To: open->feedback > State-Changed-By: bangerth > State-Changed-When: Mon Feb 3 20:51:48 2003 > State-Changed-Why: > Hm, more questions: I tried this testcase on a x86 Linux > box. Without optimization, it takes at a max 14 MB of > memory (3.2.2 prerelease), when watched with "top". With -O3, > this increases to about 22 MB. This does not seem like an > unreasonable increase. I can, but it'll take some time. I also should have underlined the fact that I have no problems using the same gcc release in other, non-Tru64, boxes. > Can you tell us what these numbers are on your machine (i.e. > without and with -O3)? > > Thanks > Wolfgang > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8559 -- Jarkko Hietaniemi <jhi@iki.fi> http://www.iki.fi/jhi/ "There is this special biologist word we use for 'stable'. It is 'dead'." -- Jack Cohen
next reply other threads:[~2003-02-03 21:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-03 21:16 Jarkko Hietaniemi [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-04 15:36 Wolfgang Bangerth 2003-02-04 9:36 Jarkko Hietaniemi 2003-02-03 21:26 Wolfgang Bangerth 2003-02-03 20:51 bangerth 2003-02-03 20:44 bangerth 2003-02-03 6:06 Jarkko Hietaniemi 2003-02-02 23:01 bangerth
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=20030203211601.23002.qmail@sources.redhat.com \ --to=jhi@iki.fi \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).