linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:28:26 +0400	[thread overview]
Message-ID: <f19298770807221028x4f2dca08l36a31a9c381bf4f3@mail.gmail.com> (raw)
In-Reply-To: <118833cc0807221020m44938f77l70324a548baa4551@mail.gmail.com>

On Tue, Jul 22, 2008 at 9:20 PM, Morten Welinder <mwelinder@gmail.com> wrote:
> On Tue, Jul 22, 2008 at 1:00 PM, Alexey Zaytsev
> <alexey.zaytsev@gmail.com> wrote:
>> [Added the new address to the CC]
>
> ("troll.com" is a bitkeeper bug.  Use a machine named "troll" and
> bitkeeper would
> happily add ".com".)
>
> With respect to the substance, I am not sure why you want to remove -specs.
> It was never meant to take a filename -- it takes a token like "i86" and adds
> options for that.  That is not generally very useful, but has its uses
> for cross-
> compilation.

But won't gcc fail in such case? Maybe we should not remove, but replace it
with a unique option to specify for which architecture sparse should check?

>
> Morten
>

  reply	other threads:[~2008-07-22 17:28 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 [this message]
2008-07-22 17:43       ` Morten Welinder
2008-07-22 17:59         ` Alexey Zaytsev
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=f19298770807221028x4f2dca08l36a31a9c381bf4f3@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).