public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Terry Guo <flameroc@gmail.com>
To: "Jędrzej Dudkiewicz" <jedrzej.dudkiewicz@gmail.com>,
	gcc <gcc-help@gcc.gnu.org>
Subject: Re: Unable to use bool type in i386.h
Date: Fri, 22 Nov 2013 14:34:00 -0000	[thread overview]
Message-ID: <CAGbRaL5g9Cxan5WDgyXWbz81UGBHLHee94ONbgNc=gatAouxFQ@mail.gmail.com> (raw)
In-Reply-To: <CABJqhQOf-uMVq71_dVQ1pxZyX0Pd9yYW3PdYNHP5vk3hYFJPUw@mail.gmail.com>

On Fri, Nov 22, 2013 at 10:02 PM, Jędrzej Dudkiewicz
<jedrzej.dudkiewicz@gmail.com> wrote:
> On Fri, Nov 22, 2013 at 2:59 PM, Terry Guo <flameroc@gmail.com> wrote:
>> On Fri, Nov 22, 2013 at 8:53 PM, Rob <robpilling@gmail.com> wrote:
>>> It seems that C files include this, so you'll want _Bool, or just use an int.
>>>
>>
>> Thanks for your reply. I know I can use the int. But the bool type is
>> more precise. And now GCC is in C++, the bool type should be
>> supported. I am curious whether this is a missing part of GCC. Can
>> someone please help to confirm?
>
> I'm not an expert, but it seems that you are compiling *.c files. GCC
> being written in C++ does not change C language in any way, so bool
> won't work.
> --
> Jędrzej Dudkiewicz
>

But if you search i386.c, you will find many bool type variables. Why
it works for i386.c but not for i386.h?

BR,
Terry

  parent reply	other threads:[~2013-11-22 14:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22 12:54 Terry Guo
2013-11-22 13:59 ` Rob
2013-11-22 14:09   ` Terry Guo
     [not found]     ` <CABJqhQOf-uMVq71_dVQ1pxZyX0Pd9yYW3PdYNHP5vk3hYFJPUw@mail.gmail.com>
2013-11-22 14:34       ` Terry Guo [this message]
2013-11-22 14:34         ` Jonathan Wakely
2013-11-22 14:38           ` Terry Guo
2013-11-22 14:57             ` Terry Guo
2013-11-22 19:40               ` Jonathan Wakely
2013-11-24 20:19             ` Ángel González
2013-11-25 17:50               ` Terry Guo

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='CAGbRaL5g9Cxan5WDgyXWbz81UGBHLHee94ONbgNc=gatAouxFQ@mail.gmail.com' \
    --to=flameroc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jedrzej.dudkiewicz@gmail.com \
    /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).