This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: SIGN_EXTRACT feature, perhaps
- To: Alasdair Baird <alasdair at wildcat dot demon dot co dot uk>, egcs-bugs at egcs dot cygnus dot com
- Subject: Re: SIGN_EXTRACT feature, perhaps
- From: Richard Henderson <rth at cygnus dot com>
- Date: Wed, 7 Apr 1999 02:35:39 -0700
- References: <199903302038.WAA00295@wildcat.demon.co.uk>
On Tue, Mar 30, 1999 at 10:38:35PM +0200, Alasdair Baird wrote:
> while (GET_CODE (inner_dest) == STRICT_LOW_PART
> || GET_CODE (inner_dest) == SUBREG
> || GET_CODE (inner_dest) == ZERO_EXTRACT)
> inner_dest = XEXP (inner_dest, 0);
>
> <blah blah>
>
> Now I might be barking mad, but should this while loop not also have a check
> for the code SIGN_EXTRACT?
No. SIGN_EXTRACT is read-only. ZERO_EXTRACT as a destination is
a bitfield insertion, and as such it doesn't matter about sign,
so we just worry about the one.
r~