9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Latchesar Ionkov <lucho@ionkov.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] gcc trouble
Date: Thu, 20 Nov 2003 09:33:56 -0500	[thread overview]
Message-ID: <20031120143356.GA20235@ionkov.net> (raw)
In-Reply-To: <f36a6d0599cdbac3fd9e21464c609297@caldo.demon.co.uk>

Hi,

I spend some time researching how to make gcc to produce Plan9 object format.

Creating a new BFD backend that generates Plan9 object files won't solve the
problem. GCC uses different calling convention, so even if we make libbfd to
produce Plan9 object format, the object files won't be compatible with
object files created by 8c.

I think the only solution is to change GCC machine description for Plan9. It
may even be possible to make gcc to generate Plan9 object files instead of
assembler files. So far I see four major tasks:

1. Change target's calling convention. This also includes finding out if the
change will affect C++ exception handling.

2. Change assembler syntax to be compatible with 8a, or make GCC to generate
Plan9 object files directly.

3. Teach 8l (and 8a) about the additional instructions that GCC can produce
(MMX, SSE etc.), or make GCC to not use them.

4. Modify 8l to support multiple definitions of GLOBAL DATA symbols, placing
only one in the image (similar to setting bit 2 of the TEXT symbol flags).

Any thoughts?

Thanks,
	Lucho

On Wed, Nov 12, 2003 at 11:46:19PM +0000, Charles Forsyth said:
> >>I guess (didn't look into it) Plan9 object format doesn't support sections
> >>with arbitrary names.
>
> it isn't the usual object format:
> see thompson's paper on the compiler (to begin with).


  reply	other threads:[~2003-11-20 14:33 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-07 16:27 cej
2003-11-07 17:58 ` mirtchov
2003-11-07 16:53   ` Russ Cox
2003-11-07 19:14     ` mirtchov
2003-11-07 19:36       ` Russ Cox
2003-11-07 19:48       ` mirtchov
2003-11-07 19:56         ` Christopher Nielsen
2003-11-07 20:47           ` ron minnich
2003-11-07 21:05             ` Christopher Nielsen
2003-11-07 21:11       ` Charles Forsyth
2003-11-07 22:34         ` mirtchov
2003-11-08  0:08     ` Latchesar Ionkov
2003-11-08  1:35       ` Russ Cox
2003-11-08  1:54         ` Latchesar Ionkov
2003-11-08  2:14           ` Russ Cox
2003-11-08  4:35           ` ron minnich
2003-11-08  4:57             ` Geoff Collyer
2003-11-08  5:05               ` ron minnich
2003-11-08  8:24                 ` Charles Forsyth
2003-11-08 17:29                   ` ron minnich
2003-11-10 10:01                   ` Douglas A. Gwyn
2003-11-11  0:16               ` Latchesar Ionkov
2003-11-12 23:46                 ` Charles Forsyth
2003-11-20 14:33                   ` Latchesar Ionkov [this message]
2003-11-20 18:34                     ` boyd, rounin
2003-11-20 21:14                       ` Latchesar Ionkov
2003-11-20 21:27                         ` boyd, rounin
2003-11-20 21:35                           ` mirtchov
2003-11-20 22:45                           ` Latchesar Ionkov
2003-11-21 10:02                         ` Fco.J.Ballesteros
2003-11-20 19:27                     ` Joel Salomon
2003-11-20 20:03                       ` Peter Bosch
2003-11-20 20:49                       ` Christopher Nielsen
2003-11-20 21:01                         ` boyd, rounin
2003-11-20 23:11                           ` Joel Salomon
2003-11-20 23:28                             ` boyd, rounin
2003-11-21  0:19                             ` Christopher Nielsen
2003-11-21  0:31                               ` boyd, rounin
2003-11-10 15:53           ` Joel Salomon
2003-11-11  7:01 cej
2003-11-11  7:05 cej
2003-11-21  7:08 cej
2003-11-21  8:46 ` Charles Forsyth
2003-11-21  9:53   ` Skip Tavakkolian

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=20031120143356.GA20235@ionkov.net \
    --to=lucho@ionkov.net \
    --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).