Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Neil Booth <neil@daikokuya.co.uk>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [TESTSUITE] assert (char == signed char)
Date: Wed, 14 Aug 2002 15:47:00 -0000	[thread overview]
Message-ID: <3D5AD966.83B6ADB@redhat.com> (raw)
In-Reply-To: <20020814220650.GB12340@daikokuya.co.uk>

Neil Booth wrote:
> 
> Michael Snyder wrote:-
> 
> > There seem to be some tests in the testsuite that are
> > based on the assumption that chars are signed, and that
> > will fail if they are unsigned.
> >
> > Eg:
> > sizeof.exp: check valueof ((int) (char)) -1 == -1
> > (prints 255 if char == unsigned)
> >
> > pointers.exp: ptype pC
> > (outputs "unsigned char *" if char == unsigned)
> >
> > Any thoughts?  Should these be regularized to accept unsigned?
> > Should it be based on a configure variable?
> 
> I'd pass -fsigned-char; that's done in some other tests.

To gcc?  Problem is, what if it isn't gcc?  As eg. Irix cc?


  reply	other threads:[~2002-08-14 22:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-14 14:28 Michael Snyder
2002-08-14 15:07 ` Neil Booth
2002-08-14 15:47   ` Michael Snyder [this message]
2002-08-15 11:31     ` Andrew Cagney

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=3D5AD966.83B6ADB@redhat.com \
    --to=msnyder@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=neil@daikokuya.co.uk \
    /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