Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Cc: Mark Wielaard <mjw@redhat.com>
Subject: Re: [RFA/commit] Remove use of stdbool.h in GDB sources.
Date: Fri, 27 Feb 2015 09:50:00 -0000	[thread overview]
Message-ID: <54F03DD8.8080902@redhat.com> (raw)
In-Reply-To: <1425027226-23546-1-git-send-email-brobecker@adacore.com>

On 02/27/2015 08:53 AM, Joel Brobecker wrote:
> Hello,
> 
> Using type bool from stdbool unfortunately causes problems trying
> to build GDB on AiX and Solaris:

Darn...


> But, thinking beyond this very specific issue, it shows that using
> stdbool.h is going to cause problems on these systems until either
> GCC fixes those includes in a way that makes them work (not really
> an option in the short term); or we switch to C++.

> 
> In the meantime, I think the path of least resistance is to revert
> the use of stdbool.h, and use integers, the way we've done up until
> now. The benefits of using type "bool" are modest, IMO, so not
> a great loss, and a temporary one.

I agree.

> 
> gdb/ChangeLog:
> 
>         * utils.h: Remove <stdbool.h> #include.
>         (producer_is_gcc): Change return type to "int".
>         * utils.c (producer_is_gcc): Change return type to int.
>         Return 1 instead of true, and 0 instead of false.
>         Adjust function documentation accordingly.
> 
> I will push this patch in the next few days, unless there are
> objections.

No objections here.

(guess we should reinstate the ARI bool rule too then.)

Thanks,
Pedro Alves


  reply	other threads:[~2015-02-27  9:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27  8:53 Joel Brobecker
2015-02-27  9:50 ` Pedro Alves [this message]
2015-03-02 14:10   ` Joel Brobecker

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=54F03DD8.8080902@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mjw@redhat.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