All of lore.kernel.org
 help / color / mirror / Atom feed
From: rubisher <rubisher@scarlet.be>
To: Chris Li <christ.li@gmail.com>
Cc: Bert Wesarg <bert.wesarg@googlemail.com>, linux-sparse@vger.kernel.org
Subject: Re: cgcc and REAL_CC help
Date: Mon, 21 Dec 2009 16:42:01 +0000	[thread overview]
Message-ID: <4B2FA559.4040102@scarlet.be> (raw)
In-Reply-To: <70318cbf0912201445m37b31c71r6209a26b40892461@mail.gmail.com>

Hello Chris,

Chris Li wrote:
> On Fri, Dec 18, 2009 at 9:14 AM, rubisher <rubisher@scarlet.be> wrote:
>> That said, my next issue is that "-E" which is disable by cgcc:
>> [snip]
>>    # If someone adds "-E", don't pre-process twice.
>>    $do_compile = 0 if $_ eq '-E';
>> [snip]
>>
>> If ever some of you knows why, I would be interested in?
> 
> My guess is that, both gcc and sparse pre-process print to stdout.
> So allow them both pre-process will mess up the result.
> 
That was also my guess but when I comment out this line and run the same script one time with 'REAL_CC=gcc-4.4 cgcc' and the
second time with 'gcc-4.4' the results are the same, thought?

> The current cgcc chose to let sparse do the pre-process and don't
> run the real cc. You can make the gcc does the real pro-process and
> sparse just check though.
> 
Yes I think that I would have to do more effort to sparse this code.

Tx,
	J.

> Chris
> 



      reply	other threads:[~2009-12-21 16:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17  9:15 cgcc and REAL_CC help rubisher
2009-12-17  9:42 ` Bert Wesarg
2009-12-18 17:14   ` rubisher
2009-12-20 22:45     ` Chris Li
2009-12-21 16:42       ` 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=4B2FA559.4040102@scarlet.be \
    --to=rubisher@scarlet.be \
    --cc=bert.wesarg@googlemail.com \
    --cc=christ.li@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.