From: Richard Zidlicky <Richard.Zidlicky@stud.informatik.uni-erlangen.de>
To: Richard Henderson <rth@redhat.com>
Cc: Peter.Barada@motorola.com, gcc@gcc.gnu.org
Subject: Re: ICE building glibc-2.2.5 using m68k-linux gcc-3.1
Date: Fri, 26 Jul 2002 15:52:00 -0000 [thread overview]
Message-ID: <20020726135349.A1114@linux-m68k.org> (raw)
In-Reply-To: <20020725180431.A27259@redhat.com>; from rth@redhat.com on Thu, Jul 25, 2002 at 06:04:31PM -0700
On Thu, Jul 25, 2002 at 06:04:31PM -0700, Richard Henderson wrote:
> On Thu, Jul 25, 2002 at 03:33:20PM -0400, Peter Barada wrote:
> > (gdb) call debug_rtx(set)
> >
> > (set (strict_low_part (reg:HI 6 %d6))
> > (reg:HI 30))
>
> This is wrong. The argument to STRICT_LOW_PART must always be
> a SUBREG of a REG.
so the responsible pattern seems to be
(define_expand "zero_extendhisi2"
[(set (match_operand:SI 0 "register_operand" "")
(const_int 0))
(set (strict_low_part (match_dup 2))
(match_operand:HI 1 "general_operand" ""))]
""
"
{
operands[1] = make_safe_from (operands[1], operands[0]);
operands[2] = gen_lowpart (HImode, operands[0]);
}")
Funny enough, the m68k version of zero_extendhisi2 insn pattern
is part of the gcc internals docs for 3.x and it is written
differently there, with an (subreg:HI ...) so I am trying this
variant now - anyone remembers when or why it was changed?
Richard
next prev parent reply other threads:[~2002-07-26 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 17:22 Peter Barada
2002-07-25 13:32 ` Richard Zidlicky
2002-07-25 15:45 ` Peter Barada
2002-07-26 8:50 ` Richard Henderson
2002-07-26 15:52 ` Richard Zidlicky [this message]
2002-07-27 15:18 ` Richard Zidlicky
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=20020726135349.A1114@linux-m68k.org \
--to=richard.zidlicky@stud.informatik.uni-erlangen.de \
--cc=Peter.Barada@motorola.com \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.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).