From: "Paulo J. Matos" <pocmatos@gmail.com>
To: gcc@gcc.gnu.org
Subject: Re: avr compilation
Date: Fri, 18 Mar 2011 13:40:00 -0000 [thread overview]
Message-ID: <ilvnab$8td$2@dough.gmane.org> (raw)
In-Reply-To: <4D835D8A.5000400@gjlay.de>
On 18/03/11 13:26, Georg-Johann Lay wrote:
> note that the last moves are two QI moves, the add is HI.
>
Yes, correct, this seems to cause some confusion on gcc side then... humm!
> Without splitting HI the moves will disappear, try -fno-split-wide-types.
>
It does work! It's enabled by -O1, maybe it should be disabled by -Os if
it improves the code size consistently.
>
> Try newer version of gcc, like 4.5.2
>
Thanks, I will. Hopefully it will do the optimisation out of the box
without the need for the extra option.
Cheers,
--
PMatos
next prev parent reply other threads:[~2011-03-18 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 8:48 Paulo J. Matos
2011-03-18 10:08 ` WANG.Jiong
2011-03-18 10:15 ` Paulo J. Matos
2011-03-18 12:11 ` David Brown
2011-03-18 13:37 ` Paulo J. Matos
2011-03-18 13:26 ` Georg-Johann Lay
2011-03-18 13:40 ` Paulo J. Matos [this message]
2011-03-18 14:20 ` Ian Lance Taylor
2011-03-18 14:50 ` Paulo J. Matos
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='ilvnab$8td$2@dough.gmane.org' \
--to=pocmatos@gmail.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).