From: Sergei Poselenov <sposelenov@emcraft.com>
To: Andrew Haley <aph@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: powercp-linux cross GCC 4.2 vs GCC 4.0.0: -Os code size regression?
Date: Wed, 16 Jan 2008 17:14:00 -0000 [thread overview]
Message-ID: <478E3A4F.7070700@emcraft.com> (raw)
In-Reply-To: <18318.13924.827172.239806@zebedee.pink>
Hello Andrew,
> Now, I sympathize that in your particular case you have a code size
> regression. This happens: when we do optimization in gcc, some code
> bases will lose out. All that we can promise is that we try not to
> make it worse for most users.
>
> What we can do is compare your code that has got much worse, and try
> to figure out why.
>
Would the generated asm listings be enough? Or should I send
the preprocessed sources as well?
Thanks a lot!
Regards,
Sergei
> Andrew.
>
next prev parent reply other threads:[~2008-01-16 17:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 11:24 Sergei Poselenov
2008-01-16 12:15 ` Duncan Sands
2008-01-16 12:19 ` Sergei Poselenov
2008-01-16 12:35 ` Duncan Sands
2008-01-16 13:20 ` Andrew Haley
2008-01-16 13:17 ` Andrew Haley
2008-01-16 15:59 ` Sergei Poselenov
2008-01-16 17:10 ` Andrew Haley
2008-01-16 17:14 ` Sergei Poselenov [this message]
2008-01-16 19:36 ` Andrew Haley
2008-01-17 14:52 ` powercp-linux cross GCC 4.2 vs GCC 4.0.0: -Os code size regression? [Emcraft #11717] Sergei Poselenov
2008-01-17 15:11 ` Richard Guenther
2008-01-17 18:27 ` Gabriel Paubert
2008-01-19 16:26 ` Andrew Haley
2008-01-19 16:35 ` David Edelsohn
2008-01-19 16:51 ` Andrew Haley
2008-01-19 19:10 ` David Edelsohn
2008-01-21 17:25 ` powercp-linux cross GCC 4.2 vs GCC 4.0.0: -Os code size regression? (filed bug 34903)[Emcraft #11717] Sergei Poselenov
2008-01-17 12:14 ` powercp-linux cross GCC 4.2 vs GCC 4.0.0: -Os code size regression? Gabriel Paubert
2008-01-17 12:47 ` Sergei Poselenov
2008-01-17 13:10 ` Gabriel Paubert
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=478E3A4F.7070700@emcraft.com \
--to=sposelenov@emcraft.com \
--cc=aph@redhat.com \
--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).