Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: cgd@broadcom.com
To: "Richard Sandiford" <rsandifo@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: sim/mips patch: add support for more NEC VR targets
Date: Wed, 06 Nov 2002 10:44:00 -0000	[thread overview]
Message-ID: <yov5el9yfsig.fsf@broadcom.com> (raw)
In-Reply-To: "Richard Sandiford"'s message of "05 Nov 2002 16:20:00 +0000"

At 05 Nov 2002 16:20:00 +0000, Richard Sandiford wrote:
> [ ... ]
> Please install if OK.
> [ ... ]
> 
> common/
> 	* Make-common.in (SIM_EXTRA_DISTCLEAN): New macro.
> 	(distclean): Depend on it.
> 
> igen/
> 	* gen-engine.c (print_engine_issue_prefix_hook): Don't add the
> 	global prefix to ENGINE_ISSUE_PREFIX_HOOK.
> 	(print_engine_issue_postfix_hook): Likewise ENGINE_ISSUE_POSTFIX_HOOK.

I've installed both of these (the former seeming obvious enough and
the latter not getting any comment from others after repeated tries
8-).

I'm still chewing on:

> mips/
> 	* configure.in (mips64vr*): Define TARGET_ENABLE_FR to 1.
> 	(mips64vr-*-*, mips64vrel-*-*): New configurations.
> 	Add a new simulator generator, MULTI.
> 	* configure: Regenerate.
> 	* Makefile.in (SIM_MULTI_OBJ, SIM_EXTRA_DISTCLEAN): New variables.
> 	(multi-run.o): New dependency.
> 	(SIM_MULTI_ALL, SIM_MULTI_CONFIGS): New variables.
> 	(BUILT_SRC_FROM_MULTI): New variable.  Depend on tmp-multi.
> 	(tmp-mach-multi, tmp-itable-multi, tmp-run-multi): New dependencies.
> 	(tmp-multi): Combine them.
> 	(clean-extra): Remove sources in BUILT_SRC_FROM_MULTI.
> 	(distclean-extra): New rule.
> 	* sim-main.h: Include bfd.h.
> 	(MIPS_BFD_MACH): New macro.
> 	* mips.igen (vr4120, vr5400, vr5500): New models.
> 	(check_mf_cycles): Don't enforce mflo and mfhi separation
> 	in vr5500 code.
> 	(clo, clz, dclo, dclz, madd, maddu, msub, msub, mul): Add *vr5500.
> 	* vr.igen: Replace with new version.
> 	* multi-run.c: New file.

I'm thinking that MIPS_BFD_MACH isn't quite right as-is, but it's
probably easier for me to fix it than to describe in vague terms what
I think it should be and then have you try to implement it. 8-)

However, before I decide, I need to fiddle with it a little bit more.



cgd


  reply	other threads:[~2002-11-06 18:44 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 [this message]
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
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=yov5el9yfsig.fsf@broadcom.com \
    --to=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