From: Andrew Cagney <ac131313@redhat.com>
To: cgd@broadcom.com
Cc: rsandifo@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: sim/mips patch: add support for more NEC VR targets
Date: Wed, 06 Nov 2002 17:40:00 -0000 [thread overview]
Message-ID: <3DC9C49D.2090801@redhat.com> (raw)
In-Reply-To: <yov5wunqyxr0.fsf@broadcom.com>
> At Wed, 06 Nov 2002 19:46:07 -0500, Andrew Cagney wrote:
>
>> >> - gen-engine.c adds the global prefix to the beginning of
>> >> ENGINE_ISSUE_(PREFIX|POSTFIX)_HOOK. It seems MIPS is the
>> >> only back-end to define these macros, and it never adds a
>> >> prefix. The patch adjusts igen accordingly.
>
>> >
>> >
>> > Hmm. I don't know igen so well. Andrew? What are your thoughts
>> > here?
>
>>
>> [I suspect its already been committed]
>> So, how did it ever build?
>
>
> Err, well, build is no problem: the code in question did #if
> defined(%sENGINE_ISSUE_PREFIX_HOOK)... so it won't get in there.
>
>
>
>> Specify two functions. One for the mips5500 and one for the rest. That
>> way, there isn't any reason for adding TATE_ARCHITECTURE (SD)->mach ==
>> bfd_mach_mips5500.
>>
>> It will also solve the default machine problem.
>
>
> well:
>
> (1) w/ separate fn, you'd need to tag _all_ of the 5500 machine insns
> w/ mips5500. (as opposed to ISA + a few mips5500 extensions.)
Er, all the instructions that belonged to the MIPS 5500 should be taged
with 5500 anyway. As I noted:
> The real world order is: ISA YYY implements MIPS XXX, BUT with a few tiny exceptions .... You end up having to check that every single *&@^#$(*&@#$ instruction matches the generic ISA. Sigh.
Andrew
next prev parent reply other threads:[~2002-11-07 1:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 9:44 Richard Sandiford
[not found] ` <mailpost.1033749908.1650@news-sj1-1>
2002-10-04 10:54 ` cgd
2002-10-09 7:14 ` Richard Sandiford
2002-10-22 15:27 ` cgd
2002-11-05 8:20 ` Richard Sandiford
2002-11-06 10:44 ` cgd
2002-11-06 14:46 ` cgd
2002-11-06 15:08 ` cgd
2002-11-26 4:44 ` Richard Sandiford
[not found] ` <mailpost.1038314670.25092@news-sj1-1>
2002-11-26 12:49 ` cgd
2002-11-26 16:55 ` Andrew Cagney
[not found] ` <mailpost.1038358543.15485@news-sj1-1>
2002-11-26 17:48 ` cgd
2002-11-26 19:10 ` Andrew Cagney
[not found] ` <mailpost.1038366650.19029@news-sj1-1>
2002-12-03 9:17 ` cgd
2002-12-03 9:35 ` Andrew Cagney
2003-01-05 7:57 ` cgd
2003-01-05 11:51 ` Richard Sandiford
[not found] ` <mailpost.1041767504.18587@news-sj1-1>
2003-01-06 7:18 ` cgd
2002-11-06 16:46 ` Andrew Cagney
2002-11-06 17:28 ` cgd
2002-11-06 17:40 ` Andrew Cagney [this message]
2002-11-07 11:08 ` cgd
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=3DC9C49D.2090801@redhat.com \
--to=ac131313@redhat.com \
--cc=cgd@broadcom.com \
--cc=gdb-patches@sources.redhat.com \
--cc=rsandifo@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