From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Josh Triplett <josh@freedesktop.org>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: [PATCH 0/5] Sparse on Cygwin (and git).
Date: Tue, 22 May 2007 18:56:29 +0100 [thread overview]
Message-ID: <46532ECD.2020502@ramsay1.demon.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2358 bytes --]
Hi Josh,
Since git uses sparse in it's "check" make target, I decided to download the
(then current) 0.2 tar-ball and see what sparse was about. Unfortunately, at present,
I am using cygwin on win32 until I get around to installing Linux. ;-)
Hence, the following patch series...
0001-Add-support-for-WIN32-attribute-names.patch
0002-Fix-an-__attribute__-parsing-error.patch
0003-Add-cygwin-support-to-cgcc.patch
0004-Fix-a-Wtypesign-bug.patch
Well, when the 0.3 tar-ball was released, I had to update the patch series.
Changes to the attribute parsing code meant an update to patch 0001 was
required. Patch 0004 now seems to be unnecessary (probably due to commit
ef2596162115bfdc2a1d3639ac99dd3ba2a71af2). Also compilation errors lead to
the introduction of two new patches (1&2/5), as follows ...
0001-Fix-an-attribute-__sentinel__-unknown-warning.patch
0002-Fix-some-enum-value-XXX-not-handled-in-switch-wa.patch
0003-Add-support-for-WIN32-attribute-names.patch
0004-Fix-an-__attribute__-parsing-error.patch
0005-Add-cygwin-support-to-cgcc.patch
As I am somewhat bandwidth challenged, until recently, I had never cloned a
git repository (not even the git repo). So, last week I cloned the sparse
repository; thankfully it only took about ten minutes (yep a slow pipe!).
Thus, again I had to update the patch series. Patch 0003 overlapped a
recent commit (baf2c5a8) by Michael Stefaniuc and patch 0004 required an
update due to handle_attributes() gaining a third parameter. So the final
patch series is:
0001-Fix-an-__sentinel__-attribute-directive-ignored.patch
0002-Fix-some-enum-value-XXX-not-handled-in-switch-wa.patch
0003-Add-more-support-for-WIN32-attribute-names.patch
0004-Fix-an-__attribute__-parsing-error.patch
0005-Add-cygwin-support-to-cgcc.patch
which was built on top of: 0.3-15-gb5bd30f
I have attached "0004-Fix-a-Wtypesign-bug.patch" simply out of interest, as
it does not require the parameter type of "function returning..." to decay to
"pointer to function returning...". The test case comes from git:
$cat tsb.c
typedef int erf(const char *r, const unsigned char *s, int f, void *c);
extern int fer(erf, void *);
static int ar(const char *r, const unsigned char *s, int f, void *c)
{
return 0;
}
int main (int argc, char *argv[])
{
fer(ar, (void *)0);
}
$
Hope you find this useful.
All the best,
Ramsay Jones
[-- Attachment #2: 0004-Fix-a-Wtypesign-bug.patch --]
[-- Type: application/xxxxx, Size: 1583 bytes --]
[-- Attachment #3: tsb.c --]
[-- Type: text/plain, Size: 249 bytes --]
typedef int erf(const char *r, const unsigned char *s, int f, void *c);
extern int fer(erf, void *);
static int ar(const char *r, const unsigned char *s, int f, void *c)
{
return 0;
}
int main (int argc, char *argv[])
{
fer(ar, (void *)0);
}
next reply other threads:[~2007-05-22 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 17:56 Ramsay Jones [this message]
2007-05-22 23:44 ` [PATCH 0/5] Sparse on Cygwin (and git) Josh Triplett
2007-05-24 17:11 ` Ramsay Jones
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=46532ECD.2020502@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=josh@freedesktop.org \
--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).