From: Mark Mitchell <mark@codesourcery.com>
To: bonzini@gnu.org
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: PR/32004, tree-ssa caused in/out asm constraints to often need reloads
Date: Thu, 05 Jul 2007 20:24:00 -0000 [thread overview]
Message-ID: <468D50E9.6000103@codesourcery.com> (raw)
In-Reply-To: <468D46AE.5020706@lu.unisi.ch>
Paolo Bonzini wrote:
>> if (GET_CODE (pat) == PARALLEL)
>> pat = XVECEXP (pat, 0, 0);
>> if (GET_CODE (pat) == SET
>> && ...)
>> ...
>
> Note I would still have to store XVECLEN somewhere, but I'll rewrite the
> test along these lines.
Thanks.
>> it seems like it would be better just to declare "match" to be "unsigned
>> long".
>
> Yes.
>
> Named constraints are handled in stmt.c.
Good, thanks for checking.
Patch OK with those changes.
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
next prev parent reply other threads:[~2007-07-05 20:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 10:54 Paolo Bonzini
[not found] ` <84fc9c000707050401h46157b0fye4b32c3e6b1c8063@mail.gmail.com>
2007-07-05 11:48 ` Paolo Bonzini
2007-07-05 18:34 ` Mark Mitchell
2007-07-05 19:39 ` Paolo Bonzini
2007-07-05 20:24 ` Mark Mitchell [this message]
2007-07-05 20:15 ` Paolo Bonzini
2007-07-07 16:29 ` Eric Botcazou
2007-07-07 18:24 ` Andrew Pinski
2007-07-07 18:30 ` Eric Botcazou
2007-07-09 2:23 ` Paolo Bonzini
2007-07-09 6:52 ` Eric Botcazou
2007-07-09 12:09 ` Paolo Bonzini
2007-07-09 12:32 ` Paolo Bonzini
2007-07-09 12:40 ` Richard Guenther
2007-07-09 13:01 ` Eric Botcazou
2007-07-09 13:01 ` Richard Guenther
2007-07-09 13:36 ` Eric Botcazou
2007-07-09 13:12 ` Paolo Bonzini
2007-07-09 13:23 ` Andrew Pinski
2007-07-09 13:45 ` Eric Botcazou
2007-07-09 15:33 ` Paolo Bonzini
2007-07-09 17:25 ` Eric Botcazou
2007-07-09 14:00 ` Eric Botcazou
2007-07-13 9:48 ` Paolo Bonzini
2007-07-13 13:42 ` 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=468D50E9.6000103@codesourcery.com \
--to=mark@codesourcery.com \
--cc=bonzini@gnu.org \
--cc=gcc-patches@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).