linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kamil Dudka <kdudka@redhat.com>
To: sparse <linux-sparse@vger.kernel.org>
Subject: [PATCH] linearize.h: sanitize header
Date: Thu, 6 Aug 2009 11:02:14 +0200	[thread overview]
Message-ID: <200908061102.14935.kdudka@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 153 bytes --]

Hello,

please consider applying the attached one-line patch. Feel free to choose 
better identifiers if these are not accurate enough. Thanks!

Kamil



[-- Attachment #2: 0001-linearize.h-sanitize-header.patch --]
[-- Type: text/x-patch, Size: 1139 bytes --]

From 4ad2c5943c1d0b16a19feefe721ebc53a4875a35 Mon Sep 17 00:00:00 2001
From: Kamil Dudka <kdudka@redhat.com>
Date: Thu, 6 Aug 2009 10:54:56 +0200
Subject: [PATCH] linearize.h: sanitize header

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);
 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);
-- 
1.6.2.5


             reply	other threads:[~2009-08-06  9:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06  9:02 Kamil Dudka [this message]
2009-08-06  9:23 ` [PATCH] linearize.h: sanitize header Hannes Eder
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=200908061102.14935.kdudka@redhat.com \
    --to=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).