public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "D. Jeff Dionne" <jeff@maribor.pfnet.com>
To: ian@cygnus.com (Ian Lance Taylor)
Cc: egcs@cygnus.com
Subject: Re: Writing a new BFD backend?
Date: Thu, 06 Nov 1997 12:53:00 -0000	[thread overview]
Message-ID: <199711061949.OAA06662@maribor.pfnet.com> (raw)
In-Reply-To: <199711061633.LAA22044@subrogation.cygnus.com>

> 
>    Date: Thu, 6 Nov 1997 15:46:50 +0100
>    From: Michael Schwingen <michaels@stochastik.rwth-aachen.de>
> 
>    I hope this is at least remotelt on topic here.
> 
> There is already a mailing list for BFD development discussions:
> bfd@cygnus.com.  Send a note to bfd-request@cygnus.com in order to
> join.
> 
>    Is there any hint where to start, or where to look for more information?
> 
> I'm afraid not.  The documentation is out of date and actively
> misleading.  All you can do is look at existing backends and try to
> emulate them.  In my opinion the ELF and ECOFF backends are probably
> the cleanest.

For what he needs to do, IMHO, it's quicker and far more easy to just write
a little utility that links against libbfd.a, reads the sections and builds
a file for the target.  Besides that, you get the added advantage of knowing
that your toolchain is working properly by default since it's using m68k-coff
or m68k-elf.  This is the approach I took for PalmPilot, with the vision of
producing a BFD back end eventually, but there would be problems with that
since PalmPilot apps have all sorts of resources and such, which means
might fit arbitrary sections, but also a whole lot of other things that 
don't really fit the model.

If you'd like to start with my code for this (easy to understand, and also
deals with relocation info, thanks to Kresten Krab Thorup), look at
ftp://ryeham.ee.ryerson.ca/pub/PalmOS/prc-tools.0.5.0.tar.gz and find
the obj-res and build-prc utilities.  It's all GPL'd of course.

Jeff.

> 
> If you ask on bfd@cygnus.com, others may be able to help.  I can
> answer specific questions, but general questions are tough.
> 
> Ian
> 


      reply	other threads:[~1997-11-06 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-06  6:47 Michael Schwingen
1997-11-06  8:33 ` Ian Lance Taylor
1997-11-06 12:53   ` D. Jeff Dionne [this message]

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=199711061949.OAA06662@maribor.pfnet.com \
    --to=jeff@maribor.pfnet.com \
    --cc=egcs@cygnus.com \
    --cc=ian@cygnus.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).