public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: "c.c.chen" <u87011@webmail.ice.ntnu.edu.tw>
To: cgen@sources.redhat.com
Subject: Doing a GAS port
Date: Sat, 13 Nov 2004 06:58:00 -0000	[thread overview]
Message-ID: <20041113070004.M84659@webmail.ice.ntnu.edu.tw> (raw)


Hi,
I wanted to port the GAS to a new target
I know that basically I will need to create this file:

--GAS target dependent 
  gas/config/tc-CPU.[ch]          
 
--opcode library (CGEN done this part) 
  opcodes/CPU-dis.c            
  opcodes/FOO-opc.c             

--BFD library
  bfd/{elf32|coff}-CPU.c        
  bfd/cpu-CPU.c 
  ...               

(Replace CPU with the name of my target chip)
 
I want to ask a quistion?
why CGEN doesn't do this part which generate tc-CPU.[ch] files?
(because cpu description information is not enough or other reason?) 

if it is worth writing a framewok to automaticly generate tc-CPU.[ch]( input 
CPU.cpu file )? 
(if i just want GAS produce a ELF format object file) 

c.c.chen

                 reply	other threads:[~2004-11-13  6:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20041113070004.M84659@webmail.ice.ntnu.edu.tw \
    --to=u87011@webmail.ice.ntnu.edu.tw \
    --cc=cgen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).