From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
To: Morten Welinder <mwelinder@gmail.com>
Cc: linux-sparse@vger.kernel.org, Morten Welinder <terra@gnome.org>
Subject: Re: Handling of -specs in cgcc
Date: Tue, 22 Jul 2008 21:59:44 +0400 [thread overview]
Message-ID: <f19298770807221059i607f5ea0lbe147ea360f6424b@mail.gmail.com> (raw)
In-Reply-To: <118833cc0807221043n215f5378pa3f97bdf75452d0a@mail.gmail.com>
On Tue, Jul 22, 2008 at 9:43 PM, Morten Welinder <mwelinder@gmail.com> wrote:
>> But won't gcc fail in such case?
>
> It will not fail, as gcc does not see any of it. But since the defines might
> not match what gcc runs with, you might get interesting effects.
>
Rright, it is not added to the gcc arguments. But this means that if the
build system actually passes -specs= for some reason, gcc would never
see them... On the other hand, have anyone ever seen the -specs option
used in real life?
>> Maybe we should not remove, but replace it
>> with a unique option to specify for which architecture sparse should check?
>
> That's certainly possible, but I would wait for an actual problem showing
> up before fixing anything. Right now, we can use -specs to get an idea
> what sparse would find for a different arch without actually having a gcc
> around that can cross compile.
>
> Morten
>
next prev parent reply other threads:[~2008-07-22 17:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 18:28 Handling of -specs in cgcc Alexey Zaytsev
2008-07-22 17:00 ` Alexey Zaytsev
2008-07-22 17:20 ` Morten Welinder
2008-07-22 17:28 ` Alexey Zaytsev
2008-07-22 17:43 ` Morten Welinder
2008-07-22 17:59 ` Alexey Zaytsev [this message]
2008-07-22 18:03 ` Josh Triplett
2008-07-22 18:11 ` Alexey Zaytsev
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=f19298770807221059i607f5ea0lbe147ea360f6424b@mail.gmail.com \
--to=alexey.zaytsev@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=mwelinder@gmail.com \
--cc=terra@gnome.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).