public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: gcc <gcc@gcc.gnu.org>
Subject: 3.1 perfomance problems
Date: Thu, 19 Jul 2001 10:08:00 -0000	[thread overview]
Message-ID: <3B5713F6.AA695850@linux-m68k.org> (raw)

Hi,

While testing 3.1 for the m68k, I've hit an interesting test case:
gcc.c-torture/compile/20001226-1.c. It already needs quite some time on
my i686 machine, but for m68k I had to increase the time out during 3.0
testing.
Anyway, 3.1 times out again and additionally one test fails with out of
memory error. I repeated the test under i686 and it shows the same
behavior, it just doesn't fail because it's faster and has more memory.

First, the test needs more than twice longer to complete, e.g. from
1m13.028s now to 2m52.571s. Adding -ftime-report shows an interesting
entry:

 cfg cleanup           :  81.12 (49%) usr   0.00 ( 0%) sys  81.13 (48%)
wall

This doesn't exists in 3.0 and 3.1 spends half the time here for this
test case.

Second, the test with '-Os' needs more than twice as much memory. top
shows normally peaks of 50MB, but with '-Os' it needs up to 115MB and
nothing of this is visible with -fmem-report.

This behavior is new in 3.1 and I didn't find anything about this in the
archives (at least not such drastic examples), so maybe this helps to
improve this.

bye, Roman

                 reply	other threads:[~2001-07-19 10:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3B5713F6.AA695850@linux-m68k.org \
    --to=zippel@linux-m68k.org \
    --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).