public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Barada <pbarada@mail.wm.sps.mot.com>
To: rth@redhat.com
Cc: Peter.Barada@motorola.com, gcc@gcc.gnu.org, Peter.Barada@motorola.com
Subject: Re: Restricted addressing modes in ColdFire FPU for DFmode
Date: Mon, 10 Dec 2001 08:15:00 -0000	[thread overview]
Message-ID: <200112101607.fBAG7Pv24134@hyper.wm.sps.mot.com> (raw)
In-Reply-To: <20011208190919.B16973@redhat.com> (message from Richard Henderson on Sat, 8 Dec 2001 19:09:19 -0800)


>> With the previous changes that I've made to add a cannot_combine flag
>> to tell the cominber that it shouldn't combine the following:
>> 
>> (insn 8 6 9 (set (reg:SI 31)
>>         (symbol_ref:SI ("zat"))) -1 (nil)
>>     (expr_list:REG_EQUAL (symbol_ref:SI ("zat"))
>>         (nil)))
>> 
>> (insn/C 9 8 11 (set (reg:DF 30)
>>         (mem:DF (reg:SI 31) 0)) -1 (nil)
>>     (nil))
>
>This is incorrect.  If you'd defined a legitimate address
>properly, you wouldn't be having this problem.

Is that GO_IF_LEGITMATE_ADDRESS()?

-- 
Peter Barada                                   Peter.Barada@motorola.com
Wizard                                         781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola)   781-270-0193 (fax)

  reply	other threads:[~2001-12-10 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 17:35 Re^2: " Peter Barada
2001-12-08 22:46 ` Richard Henderson
2001-12-10  8:15   ` Peter Barada [this message]
2001-12-10 13:11     ` Richard Henderson
2001-12-10 13:59       ` Peter Barada
2001-12-10 15:06         ` Peter Barada
  -- strict thread matches above, loose matches on Subject: below --
2001-12-07 10:13 Peter Barada
2001-12-07 11:27 ` Alan Lehotsky
2001-12-07 13:01   ` Peter Barada

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=200112101607.fBAG7Pv24134@hyper.wm.sps.mot.com \
    --to=pbarada@mail.wm.sps.mot.com \
    --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).