From: Richard Henderson <rth@redhat.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Eric Botcazou <ebotcazou@adacore.com>,
gcc-patches@gcc.gnu.org,
Richard Guenther <rguenther@suse.de>
Subject: Re: [PATCH][RFC][1/2] Bitfield lowering, add BIT_FIELD_EXPR
Date: Thu, 16 Jun 2011 19:53:00 -0000 [thread overview]
Message-ID: <4DFA5C84.80001@redhat.com> (raw)
In-Reply-To: <BANLkTimCNQRZVirf_-f1jHF6P5jeuEUBiw@mail.gmail.com>
On 06/16/2011 12:14 PM, Richard Guenther wrote:
> On Thu, Jun 16, 2011 at 7:24 PM, Eric Botcazou <ebotcazou@adacore.com> wrote:
>>> I think this would be clearer with a name like DEPOSIT_EXPR,
>>> similar to the ia64 deposit instruction.
>>
>> ia64's demise wasn't entirely undeserved then. IMO the descriptive power of
>> DEPOSIT_EXPR is almost null. BIT_FIELD_MODIFY_EXPR or something like this.
>
> It's more like BIT_FIELD_COMPOSE_EXPR which is why I chose BIT_FIELD_EXPR,
> similar to how we have COMPLEX_EXPR which composes two scalar values.
> I don't mind changing the name though, but maybe to BIT_FIELD_COMPOSE_EXPR
> then?
That'd be fine.
> The expansion code is ad-hoc, I'm not too familiar with what utilities
> we have to do a better job here. I'll have a look at store_bit_field
> (though that sounds memory-esque).
It probably was, originally. But it's got paths through there to handle
writing into a register destination, which will wind up in in the
various insv and strict_low_part patterns that the md file supports.
r~
next prev parent reply other threads:[~2011-06-16 19:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 11:46 Richard Guenther
2011-06-16 12:06 ` Jay Foad
2011-06-16 17:18 ` Richard Henderson
2011-06-16 18:10 ` Eric Botcazou
2011-06-16 19:23 ` Richard Guenther
2011-06-16 19:53 ` Richard Henderson [this message]
2011-06-20 14:23 ` William J. Schmidt
2011-06-20 19:09 ` Andrew Pinski
2011-06-20 21:03 ` Richard Guenther
2011-06-20 21:05 ` Andrew Pinski
2011-06-19 23:45 ` William J. Schmidt
2011-06-20 13:44 ` Michael Matz
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=4DFA5C84.80001@redhat.com \
--to=rth@redhat.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=richard.guenther@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).