From: Kamil Dudka <kdudka@redhat.com>
To: Hannes Eder <hannes@hanneseder.net>
Cc: Christopher Li <sparse@chrisli.org>,
sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] make sparse headers self-compilable...
Date: Tue, 11 Aug 2009 14:59:23 +0200 [thread overview]
Message-ID: <200908111459.23341.kdudka@redhat.com> (raw)
In-Reply-To: <154e089b0908110548t33b9114ej4bf3a019ee6ab80e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 398 bytes --]
On Tuesday 11 of August 2009 14:48:39 Hannes Eder wrote:
> What about just using some forward decls instead of including the header
> files?
>
> e.g. for compile.h it is enough to have a "struct symbol;" there
> instead of the "#include <symbol.h>" to make it self-compilable.
Thanks for the hint! It's definitely better, though not sufficient in all
cases. The amended patch is attached.
Kamil
[-- Attachment #2: 0001-make-sparse-headers-self-compilable.patch --]
[-- Type: text/x-diff, Size: 2218 bytes --]
From 93455c6fe7dc84e1519bec70a9fd8625a879d791 Mon Sep 17 00:00:00 2001
From: Kamil Dudka <kdudka@redhat.com>
Date: Tue, 11 Aug 2009 14:56:53 +0200
Subject: [PATCH] make sparse headers self-compilable...
... and thus possible to include them in arbitrary order and without any
external dependencies.
Signed-off-by: Kamil Dudka <kdudka@redhat.com>
---
compile.h | 2 ++
flow.h | 5 +++++
ptrlist.h | 2 ++
scope.h | 2 ++
storage.h | 3 +++
5 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/compile.h b/compile.h
index 0db8fdb..177363a 100644
--- a/compile.h
+++ b/compile.h
@@ -1,6 +1,8 @@
#ifndef COMPILE_H
#define COMPILE_H
+struct symbol;
+
extern void emit_one_symbol(struct symbol *);
extern void emit_unit_begin(const char *);
extern void emit_unit_end(void);
diff --git a/flow.h b/flow.h
index fbc9505..370aadd 100644
--- a/flow.h
+++ b/flow.h
@@ -1,11 +1,16 @@
#ifndef FLOW_H
#define FLOW_H
+#include "lib.h"
+
extern unsigned long bb_generation;
#define REPEAT_CSE 1
#define REPEAT_SYMBOL_CLEANUP 2
+struct entrypoint;
+struct instruction;
+
extern int simplify_flow(struct entrypoint *ep);
extern void simplify_symbol_usage(struct entrypoint *ep);
diff --git a/ptrlist.h b/ptrlist.h
index dae0906..fbfc080 100644
--- a/ptrlist.h
+++ b/ptrlist.h
@@ -1,6 +1,8 @@
#ifndef PTR_LIST_H
#define PTR_LIST_H
+#include <stdlib.h>
+
/*
* Generic pointer list manipulation code.
*
diff --git a/scope.h b/scope.h
index 5f1f232..0fab286 100644
--- a/scope.h
+++ b/scope.h
@@ -9,6 +9,8 @@
* Licensed under the Open Software License version 1.1
*/
+struct symbol;
+
struct scope {
struct token *token; /* Scope start information */
struct symbol_list *symbols; /* List of symbols in this scope */
diff --git a/storage.h b/storage.h
index 610cbfd..e049e23 100644
--- a/storage.h
+++ b/storage.h
@@ -1,6 +1,9 @@
#ifndef STORAGE_H
#define STORAGE_H
+#include "allocate.h"
+#include "lib.h"
+
/*
* The "storage" that underlies an incoming/outgoing pseudo. It's
* basically the backing store for a pseudo, and may be a real hardware
--
1.6.4
next prev parent reply other threads:[~2009-08-11 12:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 20:27 [PATCH] make sparse headers self-compilable Kamil Dudka
2009-08-08 11:10 ` Kamil Dudka
2009-08-11 9:40 ` Christopher Li
2009-08-11 9:55 ` Kamil Dudka
2009-08-11 10:40 ` Kamil Dudka
2009-08-11 21:08 ` Christopher Li
2009-08-11 21:25 ` Kamil Dudka
2009-08-11 12:48 ` Hannes Eder
2009-08-11 12:59 ` Kamil Dudka [this message]
2009-08-11 21:08 ` Christopher Li
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=200908111459.23341.kdudka@redhat.com \
--to=kdudka@redhat.com \
--cc=hannes@hanneseder.net \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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).