From: Georg-Johann Lay <avr@gjlay.de>
To: gcc@gcc.gnu.org
Cc: Georg-Johann Lay <avr@gjlay.de>,
Richard Sandiford <richard.sandiford@linaro.org>
Subject: Re: IRA/reload make bulky code: why stack slots where GPR is fine?
Date: Wed, 06 Apr 2011 10:52:00 -0000 [thread overview]
Message-ID: <4D9C45EF.8090404@gjlay.de> (raw)
In-Reply-To: <g4k4f8j28n.fsf@linaro.org>
Richard Sandiford schrieb:
> Georg-Johann Lay <avr@gjlay.de> writes:
>> With new versions of gcc from trunk (like last snapshot SVN 171894), I
>> observe very bad code from register allocator.
>
> Could you check whether:
>
> http://gcc.gnu.org/ml/gcc-patches/2011-03/msg02053.html
>
> fixes the problem? It'd be nice to know if it's the same thing,
> or something else.
>
> Richard
No, that does not help. This patch is already integrated in my version.
What helps is -fno-split-wide-types
Johann
prev parent reply other threads:[~2011-04-06 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 15:18 Georg-Johann Lay
2011-04-04 18:12 ` Denis Chertykov
2011-04-05 12:46 ` Richard Sandiford
2011-04-06 10:52 ` Georg-Johann Lay [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=4D9C45EF.8090404@gjlay.de \
--to=avr@gjlay.de \
--cc=gcc@gcc.gnu.org \
--cc=richard.sandiford@linaro.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).