public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Trevor Saunders <tbsaunde@tbsaunde.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>, Jeff Law <law@redhat.com>,
	       tbsaunde+gcc@tbsaunde.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 3/8] add default for PCC_BITFIELD_TYPE_MATTERS
Date: Thu, 30 Apr 2015 12:17:00 -0000	[thread overview]
Message-ID: <20150430121333.GP1751@tucnak.redhat.com> (raw)
In-Reply-To: <20150430115718.GA1508@tsaunders-iceball.corp.tor1.mozilla.com>

On Thu, Apr 30, 2015 at 07:58:33AM -0400, Trevor Saunders wrote:
> On Thu, Apr 30, 2015 at 08:54:05AM +0200, Andreas Schwab wrote:
> > Trevor Saunders <tbsaunde@tbsaunde.org> writes:
> > 
> > >> diff --git a/libobjc/encoding.c b/libobjc/encoding.c
> > >> index 7333908..20ace46 100644
> > >> --- a/libobjc/encoding.c
> > >> +++ b/libobjc/encoding.c
> > >> @@ -1167,7 +1167,7 @@ objc_layout_structure_next_member (struct objc_struct_layout *layout)
> > >>    /* Record must have at least as much alignment as any field.
> > >>       Otherwise, the alignment of the field within the record
> > >>       is meaningless.  */
> > >> -#ifndef PCC_BITFIELD_TYPE_MATTERS
> > >> +#if !PCC_BITFIELD_TYPE_MATTERS
> > 
> > With `#define PCC_BITFIELD_TYPE_MATTERS true' this expands to `#if
> > !true' which evaluates to 1 since true isn't a defined identifier?
> 
> I think true is a defined identifier since this is compiled as c11.

true is not a defined identifier, neither in C89, nor in C99, nor in C11.
In C, true may be a macro if stdbool.h is included.
system.h has:
#undef TRUE
#undef FALSE

#ifdef __cplusplus
  /* Obsolete.  */
# define TRUE true
# define FALSE false
#else /* !__cplusplus */
# undef bool
# undef true
# undef false

# define bool unsigned char
# define true 1
# define false 0

  /* Obsolete.  */
# define TRUE true
# define FALSE false
#endif /* !__cplusplus */
if it is included.

	Jakub

  reply	other threads:[~2015-04-30 12:13 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27  5:56 [PATCH 0/8] remove more conditional compilation tbsaunde+gcc
2015-04-27  5:56 ` [PATCH 1/8] add default for NO_FUNCTION_CSE tbsaunde+gcc
2015-04-27  5:56 ` [PATCH 3/8] add default for PCC_BITFIELD_TYPE_MATTERS tbsaunde+gcc
2015-04-29 13:18   ` Andreas Schwab
2015-04-29 21:54     ` Trevor Saunders
2015-04-29 22:00       ` Andreas Schwab
2015-04-29 22:26         ` Jeff Law
2015-04-29 22:30           ` Trevor Saunders
2015-04-29 22:33             ` Jeff Law
2015-04-30  1:45               ` Trevor Saunders
2015-04-30  3:24                 ` Trevor Saunders
2015-04-30  4:13                   ` Jeff Law
2015-04-30  7:13                   ` Andreas Schwab
2015-04-30 11:59                     ` Trevor Saunders
2015-04-30 12:17                       ` Jakub Jelinek [this message]
2015-04-30 12:22                       ` Andreas Schwab
2015-04-29 22:40             ` Jeff Law
2015-04-30  6:58             ` Andreas Schwab
2015-04-30 12:34               ` Trevor Saunders
2015-04-30 12:39                 ` Jakub Jelinek
2015-04-30 13:07                   ` Trevor Saunders
2015-04-30 17:50                   ` Joseph Myers
2015-05-01  0:01                     ` Trevor Saunders
2015-04-27  5:57 ` [PATCH 4/8] add default for EPILOGUE_USES tbsaunde+gcc
2015-04-27  5:57 ` [PATCH 8/8] remove #if ARGS_GROW_DOWNWARD tbsaunde+gcc
2015-04-27  5:57 ` [PATCH 5/8] always define HAVE_simple_return and HAVE_return tbsaunde+gcc
2015-05-06  1:13   ` Mike Stump
2015-05-06  3:16     ` Trevor Saunders
2015-04-27  5:57 ` [PATCH 2/8] add default for HARD_REGNO_RENAME_OK tbsaunde+gcc
2015-04-27  5:57 ` [PATCH 6/8] always define HAVE_epilogue tbsaunde+gcc
2015-04-27  5:57 ` [PATCH 7/8] always define ARGS_GROW_DOWNWARD tbsaunde+gcc

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=20150430121333.GP1751@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=schwab@linux-m68k.org \
    --cc=tbsaunde+gcc@tbsaunde.org \
    --cc=tbsaunde@tbsaunde.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).