Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: matthew green <mrg@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: re: [patch] AltiVec support for PSIM.
Date: Thu, 03 Jan 2002 17:59:00 -0000	[thread overview]
Message-ID: <10879.1010109556@cygnus.com> (raw)
In-Reply-To: your message of "Thu, 03 Jan 2002 16:28:33 +0930." <3C340119.70201@cygnus.com>


   
   
   That just leaves the problem of how to generate an altivec enabled 
   simulator from two files.  I can think of two alternatives: steal code 
   from the more up-to-date sim/igen generator as that supports a 
   ``:include:'' directive; pull a nasty hack such as `cat ppc-instructions 
   altivec.igen > tmp.igen` comes to mind (it does defeat igen's ability to 
   refer back to source code lines though).

yup.  i had a quick look at supporting :include: but that has a few
issues with $(builddir) != $(srcdir) that don't look trivial to solve
and the sim/igen code has changed somewhat...
   
   Given that I suspect you're going to need to be able to generate 
   multiple simulators - with / without Altivec, stealing code from 
   sim/igen might be the better medium to long term option.  Since, as 
   illustrated by MIPS, sim/igen supports this.

for the short term, i'm going to go with the "cat" hack, but i will
work on making :include: work in the longer term.  as you note, the
cat solution loses the line number info.  


a third solution would be to permit multiple "-i" switches to be
passed to igen, but that also looks non-trivial.  at least the call
to insn_table_expand_insns() would need to be modified somehow, but
i could be wrong.



thanks,


.mrg.


  reply	other threads:[~2002-01-04  1:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-28 17:49 matthew green
2002-01-02 22:58 ` Andrew Cagney
2002-01-03 17:59   ` matthew green [this message]
2002-01-03 20:56     ` matthew green
2002-01-11 10:41       ` Andrew Cagney

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=10879.1010109556@cygnus.com \
    --to=mrg@cygnus.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.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