9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jens Staal <staal1978@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] plan9 vs aout
Date: Tue, 9 Jun 2020 22:02:05 +0200	[thread overview]
Message-ID: <20200609200205.57rs3fptrjwhwr33@Hugin> (raw)
In-Reply-To: <20200602123638.pj5nqzrzazt6qsv6@Hugin>

I have now added 2 more branches for reference from the updated port of gcc and
binutils to i386-plan9 from https://marcus.biz.tm/jail/ :

binutils-2_22-plan9

gcc-4.8-plan9

Hopefully there are some clues there to help making a working current i386-plan9 cross
compiler.


On Tue, Jun 02, 2020 at 02:36:38PM +0200, Jens Staal wrote:
> Dear all,
> 
> First a bit of background:
> I am currently attempting to update the old i386-plan9 target for binutils/gcc
> in order to generate a modern cross compiler targeting plan9.
> 
> I have extracted the changes done to gcc 3.0 and binutils 2.11.2 from:
> https://9p.io/sources/extra/gcc/
> 
> My binutils and gcc attempts can be found at:
> 
> https://github.com/staalmannen/gcc
> branch plan9 : porting attempt to current gcc (10)
> branch gcc-3.0-plan9 : original port added to the 3.0 branch
> 
> https://github.com/staalmannen/binutils-gdb
> branch plan9: porting attempt to current binutils (2.34)
> branch binutils-2_11-plan9 : original port added to the 2.11 branch
> 
> Definitely not just a copy-and-paste endeavour unfortunately. The old port
> almost 20 years old and some style and structure changes have happened in that
> time.
> 
> I have built a binutils variant but when I try to compile a "Hello.S" with
> i386-lucent-plan9-as and execute it under i386 9front, I get an error about
> incorrect file header, so something is wrong.
> 
> What I learned from looking at the old port and trying to adapt it to compile in
> a modern binutils background is that a lot of it is basically copied from the
> generic aout target (I have some uncommitted changes where I am updating the
> obj-plan9 files to modern modified obj-aout files with the original changes
> applied).
> 
> So to my question: what are the differences between the plan9 file format and
> what binutils would see as generic aout? 
> 
> 
> PS. If someone would be interested to help out, you are more than welcome ;) DS.
> 
> 
> 
> 
> 
> ------------------------------------------
> 9fans: 9fans
> Permalink: https://9fans.topicbox.com/groups/9fans/T0d486ca41e37210d-M9cbbb545155e2a1fd2addc16
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2020-06-09 20:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 12:36 Jens Staal
2020-06-09 20:02 ` Jens Staal [this message]
     [not found] <CAL6pNZ98fBry0Q8wmBhLDLYWnwv0Sr-MV1X_P+jCTbn4RHJPVg@mail.gmail.com>
     [not found] ` <20200617032730.tj6dxckg444u5czq@Hugin>
     [not found]   ` <CAL6pNZ-gv3qMSKH3ubyEaaeP5SvT6MzDy3hVayHnAXrSFXuHTw@mail.gmail.com>
     [not found]     ` <CAL6pNZ8NC+E_1FyYQ5i5kDTOC6DiZ_GuQwAu9A1gEWYJXBXH2Q@mail.gmail.com>
     [not found]       ` <20200617082616.qg5jv66tbpsgpy6r@Hugin>
     [not found]         ` <CAL6pNZ89Zfi8Lqb30Jvpyb3TKTE6ZAvr0yOnyVgV-LOnVyTyQg@mail.gmail.com>
     [not found]           ` <CAL6pNZ9Obue7WDGwCYmdRCGO2Otz-Y76CFQB2eVZ8L9dJJPzNw@mail.gmail.com>
     [not found]             ` <20200617121723.3kwgd45fgwv6cwg5@Hugin>
     [not found]               ` <CAL6pNZ-OJP_sZGHb2VSbk+_qYfbBGQcfmPffD--hYoz_Z+pkxg@mail.gmail.com>
     [not found]                 ` <CAL6pNZ9mvYx3_qf9gNSKbZFb8LWXCcdByH9rjcAv6HN_RZu-2Q@mail.gmail.com>
     [not found]                   ` <20200619103652.r6cv44eemckqi6zo@Hugin>
2020-06-19 15:52                     ` [9fans] " Conor Williams

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=20200609200205.57rs3fptrjwhwr33@Hugin \
    --to=staal1978@gmail.com \
    --cc=9fans@9fans.net \
    /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).