public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert de Bath <robert$@mayday.cix.co.uk>
To: Manuel Novoa III <mjn3@codepoet.org>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: More dev86 changes (0.16.7)
Date: Sat, 10 Aug 2002 21:28:14 +0100 (BST)	[thread overview]
Message-ID: <37f23ff36ac7348a@mayday.cix.co.uk> (raw)
In-Reply-To: <20020810193601.GA11440@codepoet.org>

On Sat, 10 Aug 2002, Manuel Novoa III wrote:

> Hello Robert,
>
> Sorry it took so long to do some testing, but I've been swamped.
>
> Tried to build some of my uClibc stuff and found a bug with the new cpp
> that is illustrated with the following test case.
>
> test.c:
>
>    #define X  (1UL)
>
>    #if X == 0
>    #error this shouldn't happen
Oops, you _really_ shouldn't put that "single quote" there, ansi preprocessors
that follow the standard explicitly will whinge.


>    #endif
>
> With the new cpp, what shouldn't happen... does.
> Here's the output for "ncc -ansi -E test.c".
>
>    test.c:3: warning: Unexpected text following preprocessor command
>    test.c:5: error: #error this shouldn't happen
>    # 1 "test.c"
>
> Output without -ansi is:
>
>    # 1 "test.c"
>    test.c:3: warning: Unexpected text following preprocessor command
>    test.c:5: error: #error this shouldn't happen

Okay, "UL" is now added as a valid type specifier for integers.
However specifing the type will make no difference as the integer
type for preprocessor expressions is supposed to be the largest
available integer however you express it.

I'm not even sure specifing a type is actually legal, but I think it's
covered by the phrase "identifier-nondigit" in the syntax table.

> Also, with the old cpp one could use "-I" to not include the default
> include dirs.  This feature seems to be lacking in the new version.

That is a bug in the new bcc.c that's been there since it first appeared,
(Errm, 0.16.2) ho hum nobody noticed before. (Including me!!!)

Okay fixed, and I'll be uploading a new version tomorrow with those
and a few other changes.

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                       <http://www.cix.co.uk/~mayday>



  reply	other threads:[~2002-08-10 20:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-02 20:18 More dev86 changes (0.16.7) Robert de Bath
2002-08-02 20:24 ` Manuel Novoa III
2002-08-03 10:17 ` More dev86 changes (0.16.7) [About the optimiser] Harry Kalogirou
2002-08-03 11:01   ` Robert de Bath
2002-08-03 11:31   ` Robert de Bath
2002-08-03 12:24     ` Harry Kalogirou
2002-08-10 19:36 ` More dev86 changes (0.16.7) Manuel Novoa III
2002-08-10 20:28   ` Robert de Bath [this message]
2002-08-11  1:06     ` Manuel Novoa III
2002-08-11 16:44       ` dev86-0.16.8 cpp bugs Manuel Novoa III
2002-08-11 19:19         ` Robert de Bath
2002-08-11 20:01           ` Manuel Novoa III
  -- strict thread matches above, loose matches on Subject: below --
2002-08-03  5:21 More dev86 changes (0.16.7) Ken Martwick
2002-08-03  6:12 ` Robert de Bath
2002-08-03 17:07 Ken Martwick
2002-08-03 17:14 ` Paul Nasrat

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=37f23ff36ac7348a@mayday.cix.co.uk \
    --to=robert$@mayday.cix.co.uk \
    --cc=linux-8086@vger.kernel.org \
    --cc=mjn3@codepoet.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