From: rubisher <rubisher@scarlet.be>
To: Christopher Li <sparse@chrisli.org>
Cc: Blue Swirl <blauwirbel@gmail.com>, linux-sparse@vger.kernel.org
Subject: Re: sparse 0.4.2: cgcc issue
Date: Tue, 08 Dec 2009 19:03:37 +0000 [thread overview]
Message-ID: <4B1EA309.7050106@scarlet.be> (raw)
In-Reply-To: <70318cbf0912071847s5dc57120v437ae6ea3131b143@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
Christopher Li wrote:
> On Mon, Dec 7, 2009 at 10:04 AM, Blue Swirl <blauwirbel@gmail.com> wrote:
>> My Perl skills are not very bright, but the suggested patch
>> (http://marc.info/?l=linux-sparse&m=126010091922942&w=2) looks
>> correct.
>
> Same here.
>
> Rubisher, can you please send me a Signed-Off-By: line for the patch
> you submit?
>
> Thanks
>
> Chris
>
if that could help you:
a possible fix to cgcc issue in sparse 0.4.2:
Use of uninitialized value $bits in exists at /usr/bin/cgcc line 139.
/usr/bin/cgcc: weird number of bits. at /usr/bin/cgcc line 139.
Signed-off-by: Joel Soete <rubisher@scarlet.be>
--- cgcc.orig 2009-11-28 17:41:28.000000000 +0000
+++ cgcc 2009-12-06 11:55:32.000000000 +0000
@@ -133,7 +133,7 @@
my @types = (['SCHAR',''], ['SHRT',''], ['INT',''], ['LONG','L'], ['LONG_LONG','LL'], ['LONG_LONG_LONG','LLL']);
my $result = " -D__CHAR_BIT__=$char";
- while (@types) {
+ while (@types && @_) {
my $bits = shift @_;
my ($name,$suffix) = @{ shift @types };
die "$0: weird number of bits." unless exists $pow2m1{$bits};
=== <> ===
Also attached in case of mail client issue
Tx a lot,
J.
[-- Attachment #2: CGCC.diff.gz --]
[-- Type: application/x-gzip, Size: 308 bytes --]
prev parent reply other threads:[~2009-12-08 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 22:34 sparse 0.4.2: cgcc issue rubisher
2009-12-06 12:01 ` rubisher
2009-12-07 9:10 ` Christopher Li
2009-12-07 18:04 ` Blue Swirl
2009-12-08 2:47 ` Christopher Li
2009-12-08 19:03 ` rubisher [this message]
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=4B1EA309.7050106@scarlet.be \
--to=rubisher@scarlet.be \
--cc=blauwirbel@gmail.com \
--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