From: ami_stuff <ami_stuff@o2.pl>
To: ami_stuff <ami_stuff@o2.pl>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 4..4.x speed regression - help?
Date: Mon, 17 Aug 2009 00:39:00 -0000 [thread overview]
Message-ID: <74af2d11.6acc4366.4a8812b9.bdfcd@o2.pl> (raw)
In-Reply-To: <2fdfa587.3e8d2013.4a87ec55.d57bd@o2.pl>
Hi,
The problematic source code is deflate.c from libz.
CFLAGS=-O3 -DUSE_MMAP -m68060 -fomit-frame-pointer
When I compile all source code with GCC 4.4.1, I get slow minigzip binary.
When I compile all source code with GCC 4.4.1 except deflate.c (this one I
compile with GCC 3.4.0), I get minigzip binary with normal speed.
Regards
next prev parent reply other threads:[~2009-08-16 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 16:02 ami_stuff
2009-08-16 22:46 ` Bernd Roesch
2009-08-17 0:39 ` ami_stuff [this message]
2009-08-17 6:42 ` Martin Guy
2009-08-17 8:53 ` Kenneth Hoste
2009-08-17 10:00 ` Richard Guenther
2009-08-17 9:03 ` Paolo Bonzini
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=74af2d11.6acc4366.4a8812b9.bdfcd@o2.pl \
--to=ami_stuff@o2.pl \
--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).