public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: mjn3@codepoet.org (Manuel Novoa III)
To: Riley Williams <rhw@InfraDead.Org>
Cc: Harry Kalogirou <harkal@gmx.net>,
	Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: C compiler, assembler and linker
Date: Mon, 15 Jul 2002 11:02:05 -0600	[thread overview]
Message-ID: <20020715170205.GA12650@codepoet.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0207150705440.4272-100000@Consulate.UFP.CX>

Hi Riley,

On Mon, Jul 15, 2002 at 07:07:27AM +0100, Riley Williams wrote:
> > I don't know about small C, but I managed to get bcc to build itself
> > for elks by omitting all the floating point related code. The pre-
> > processor appears to work, but the code generator dies. I haven't
> > had time to track down the problem(s).
> 
> Could you perhaps advise re the tweaks you have done so far? That way,
> we can add a few more brain cells working on sorting the problem out...

Hopefully I'll have time this evening to sort out a patch to post.
I found that dev86-0.16.3 has a number of build issues, so I had to
modify some of the makefiles, etc. as well.

Anyway, here's a list of my bcc tweaks (as best I recall):

1) #elif support.
2) #warning support (at least for non-continued lines).
3) Support asm() at file scope.  This is to allow the equivalent
   of #asm/#endasm in macros.
4) Limited support for things like "#define stdio stdio".  Stock bcc
   goes into an infinite loop when encounting this.  The implementation
   has flaws, but it does what I needed.  You see this a lot in the
   glibc headers we're using with uClibc (yes I'm working on a port).
5) Improved condition wrapping of the floating point related code in
   the bcc source (working towards building bcc for elks).  As I said,
   the code generator dies... at least using elksemu.

Manuel

  reply	other threads:[~2002-07-15 17:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-14 14:05 C compiler, assembler and linker Harry Kalogirou
2002-07-14 17:27 ` Manuel Novoa III
2002-07-15  6:07   ` Riley Williams
2002-07-15 17:02     ` Manuel Novoa III [this message]
2002-07-15 19:13       ` Riley Williams
2002-07-15 22:02         ` Manuel Novoa III
2002-07-16  6:27           ` Riley Williams
2002-07-17  1:31             ` Manuel Novoa III
2002-07-17  6:33               ` Riley Williams
2002-07-18 12:03                 ` Minix vs. ELKS Feher Tamas
2002-07-18 12:27                   ` Javier Sedano
2002-07-02 15:07                     ` (unknown) Miguel A. Bolanos
2002-07-18 13:40                   ` Minix vs. ELKS Alan Cox
2002-07-22 21:41                 ` C compiler, assembler and linker Robert de Bath
2002-07-23  8:16               ` Robert de Bath
2002-07-23 16:25                 ` Manuel Novoa III
2002-07-23 19:09                   ` Robert de Bath
2002-07-24 21:17         ` More dev86 changes (0.16.5) Robert de Bath
2002-07-24 22:02           ` Riley Williams
2002-07-25 15:42             ` Manuel Novoa III
2002-07-26  7:55               ` Robert de Bath
2002-07-26 15:12                 ` Manuel Novoa III
2002-07-26  8:22             ` Robert de Bath
2002-07-24 22:26           ` Paul Nasrat
2002-07-25 16:34             ` Manuel Novoa III
2002-07-22 23:26       ` C compiler, assembler and linker Robert de Bath
2002-07-23  0:34         ` Riley Williams
2002-07-23  0:58           ` Manuel Novoa III
2002-07-23  0:46         ` Manuel Novoa III
  -- strict thread matches above, loose matches on Subject: below --
2002-07-15 14:16 Ken Martwick
2002-07-15 19:21 ` Riley 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=20020715170205.GA12650@codepoet.org \
    --to=mjn3@codepoet.org \
    --cc=harkal@gmx.net \
    --cc=linux-8086@vger.kernel.org \
    --cc=rhw@InfraDead.Org \
    /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