public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: Bernd Schmidt <bernds@codesourcery.com>,
	gcc-patches@gcc.gnu.org, 	Andrew Pinski <pinskia@gmail.com>
Subject: Re: Patch: PR40900, extending call patterns
Date: Sat, 01 May 2010 10:45:00 -0000	[thread overview]
Message-ID: <y2rf865508f1005010344v58d6a5abi4b5ace0eec181353@mail.gmail.com> (raw)
In-Reply-To: <201005010054.17350.ebotcazou@adacore.com>

On Sat, May 1, 2010 at 00:54, Eric Botcazou <ebotcazou@adacore.com> wrote:
>> When finished, it looks like the one below.  Simply setting
>> sign_bit_copies in record_dead_and_set_regs_1 doesn't work, and rather
>> than duplicating the bookkeeping I construct a small piece of RTL to
>> pass to record_value_for_reg that makes it do the right thing.
>>
>> This works without modifying backends, but it has the drawback that it
>> can't optimize indirect calls since we're lacking a decl for them.

REG_EXPR?

> And going back to the Tree level in the RTL combiner is ugly.  Why can PowerPC
> and MIPS already optimize this and not ARM?  That's worth investigating.

True, however promote_function_mode is already being used by combine
for similar reasons (see setup_incoming_promotions), which is why I
suggested it.

Paolo

  parent reply	other threads:[~2010-05-01 10:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-30  1:05 Bernd Schmidt
2010-04-30  3:33 ` Andrew Pinski
2010-04-30  9:23   ` Paolo Bonzini
2010-04-30 15:09     ` Bernd Schmidt
     [not found]       ` <201005010054.17350.ebotcazou@adacore.com>
2010-05-01 10:45         ` Paolo Bonzini [this message]
2010-05-03  9:39         ` Bernd Schmidt
2010-05-05 13:01           ` Eric Botcazou
2010-05-06  7:14             ` Paolo Bonzini
2010-05-06  7:36               ` Eric Botcazou
2010-06-08 21:56             ` Bernd Schmidt
2010-06-09 22:14               ` Eric Botcazou
2010-06-11 13:58                 ` Bernd Schmidt
2010-06-16 21:23                   ` Eric Botcazou
2010-06-18  7:31                     ` Bernd Schmidt
2010-06-18 17:09                       ` Eric Botcazou

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=y2rf865508f1005010344v58d6a5abi4b5ace0eec181353@mail.gmail.com \
    --to=bonzini@gnu.org \
    --cc=bernds@codesourcery.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=pinskia@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).