From: Hannes Eder <hannes@hanneseder.net>
To: Kamil Dudka <kdudka@redhat.com>
Cc: sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] linearize.h: sanitize header
Date: Thu, 6 Aug 2009 11:23:26 +0200 [thread overview]
Message-ID: <154e089b0908060223h6ae15b26q73360ee3658d6a82@mail.gmail.com> (raw)
In-Reply-To: <200908061102.14935.kdudka@redhat.com>
On Thu, Aug 6, 2009 at 11:02, Kamil Dudka<kdudka@redhat.com> wrote:
> It's unfortunate to use 'true' and 'false' as identifiers in a system
> header. It clashes with corresponding macros from <stdbool.h> when
> included before <sparse/linearize.h>.
>
> Signed-off-by: Kamil Dudka <kdudka@redhat.com>
> ---
> linearize.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/linearize.h b/linearize.h
> index 2205082..50b3601 100644
> --- a/linearize.h
> +++ b/linearize.h
> @@ -328,7 +328,7 @@ struct entrypoint {
> struct instruction *entry;
> };
>
> -extern void insert_select(struct basic_block *bb, struct instruction *br, struct instruction *phi, pseudo_t true, pseudo_t false);
> +extern void insert_select(struct basic_block *bb, struct instruction *br, struct instruction *phi, pseudo_t if_true, pseudo_t if_false);
I guess it is wise to change this in linearize.c as well. Mind sending a patch?
> extern void insert_branch(struct basic_block *bb, struct instruction *br, struct basic_block *target);
>
> pseudo_t alloc_phi(struct basic_block *source, pseudo_t pseudo, int size);
Cheers,
-Hannes
next prev parent reply other threads:[~2009-08-06 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 9:02 [PATCH] linearize.h: sanitize header Kamil Dudka
2009-08-06 9:23 ` Hannes Eder [this message]
2009-08-06 9:30 ` Kamil Dudka
2009-08-06 9:39 ` Hannes Eder
2009-08-06 9:51 ` Kamil Dudka
2009-08-06 11:09 ` Hannes Eder
2009-08-06 17:10 ` Christopher Li
2009-08-06 17:27 ` Kamil Dudka
2009-08-06 17:49 ` Hannes Eder
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=154e089b0908060223h6ae15b26q73360ee3658d6a82@mail.gmail.com \
--to=hannes@hanneseder.net \
--cc=kdudka@redhat.com \
--cc=linux-sparse@vger.kernel.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 NNTP newsgroup(s).