From: Paolo Bonzini <bonzini@gnu.org>
To: Martin Guy <martinwguy@gmail.com>
Cc: ami_stuff <ami_stuff@o2.pl>, gcc@gcc.gnu.org
Subject: Re: GCC 4..4.x speed regression - help?
Date: Mon, 17 Aug 2009 09:03:00 -0000 [thread overview]
Message-ID: <4A8917E1.1060301@gnu.org> (raw)
In-Reply-To: <56d259a00908160902q54cda0a6nab0d7eb28abd8d48@mail.gmail.com>
On 08/16/2009 06:02 PM, Martin Guy wrote:
> Yes, GCC is bigger and slower and for several architectures generates
> bigger, slower code with every release, though saying so won't make
> you very popular on this list! :)
But surprise, if you report a bug, chances are it will be fixed
(especially for something as well known as gzip).
And it is actually useless to post on the mailing list, since the bug is
there for interested people anyway.
Paolo
prev parent reply other threads:[~2009-08-17 8:42 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
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 [this message]
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=4A8917E1.1060301@gnu.org \
--to=bonzini@gnu.org \
--cc=ami_stuff@o2.pl \
--cc=gcc@gcc.gnu.org \
--cc=martinwguy@gmail.com \
/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).