9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bruce Ellis <brucee@chunder.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] arm compiler info
Date: Wed,  5 May 2004 23:51:33 +1000	[thread overview]
Message-ID: <4098F165.5050504@chunder.com> (raw)
In-Reply-To: <b86d3049eb77c30b1ecca5a8e5b9b1b8@snellwilcox.com>

it isn't hard to get ELF output, both vl and el have
a flag for it so changing 5l is a snarf/paste or too.
i'm not aware of the 922 arch but i think getting 5c/5l
to accomodate it is not too hard.  charles will have
something to say i'm sure.

brucee
[compiler writer seeking work]

Steve Simon wrote:

> Hi,
>
> I'am just taking over a project at work which
> uses an embedded ARM CPU. I'am told its an ARM 9 TDMI,
> also known as an ARM 922. Anyone any idea if I could
> cross compile using the Plan9 arm compiler? Is the
> arm7 (the compiler) a subset of the arm9?
>
> Also this project uses position independant code & data
> and ELF files, doing a link/load on program startup. I could
> code aout2elf quite easily but does
>
> If the compiler is a non-starter then I may have a go at
> bringing the arm7 GCC crosscompiler up on the back
> of dhogs native GCC.
>
> I know the better solution is to modify the arm9 compiler
> but I am still up to my eyes in CIFS in my spare time so
> I cannot waste work time on playing plan9 compilers (shame).
>
> -Steve



  reply	other threads:[~2004-05-05 13:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-05 10:45 Steve Simon
2004-05-05 13:51 ` Bruce Ellis [this message]
2004-05-05 14:04   ` Steve Simon
2004-05-05 19:25     ` boyd, rounin
2004-05-06 10:05   ` [9fans] acme Zerox: Get lost Charles Forsyth
2004-05-07  0:02     ` Rob Pike
2004-05-06 10:29   ` [9fans] arm compiler info Charles Forsyth
2004-05-06 12:24     ` Steve Simon

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=4098F165.5050504@chunder.com \
    --to=brucee@chunder.com \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).