All of lore.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 16:02:08 -0600	[thread overview]
Message-ID: <20020715220208.GA15993@codepoet.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0207151956320.4272-100000@Consulate.UFP.CX>

Riley,

On Mon, Jul 15, 2002 at 08:13:01PM +0100, Riley Williams wrote:
> Can I add some wish-list items:

I've only been adding some features, like #elif and #warning, that I
tend to use in my uClibc code.  My main interest isn't in working on
bcc, but in reducing the work I need to do in porting uClibc to elks.

>   6) True support for the "signed" keyword. At the moment, any file
>      using it has to include a "#define signed" line to remove it for
>      bcc, and in some cases, even that isn't enough as the code stops
>      working as a result.

Yes, I know.  bcc supports only unsigned char.  Coding around that
limitation can be a pain.

>   7) At least a warning message if any unrecognised options are given
>      on the command line. At the moment, unrecognised options are just
>      silently ignored!

Probably not worth doing at the moment because the main bcc driver was
rewritten recently and is probably still in flux.

> Also, are there any plans to get these included in the primary bcc code?

I had planned to send my patches to the dev86 maintainer.  When I get
the patch cleaned up and post it here, I'll also forward it on to
Robert de Bath... although I've seen him post to this list on occassion.

Manuel

  reply	other threads:[~2002-07-15 22: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
2002-07-15 19:13       ` Riley Williams
2002-07-15 22:02         ` Manuel Novoa III [this message]
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
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=20020715220208.GA15993@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.