From: Christopher Li <sparse@chrisli.org>
To: Alexander Sorockin <sorockin@yandex.ru>
Cc: linux-sparse@vger.kernel.org
Subject: Re: `char * s = "abc";' causes compile to crash with a segfault
Date: Thu, 30 Apr 2009 02:16:49 -0700 [thread overview]
Message-ID: <70318cbf0904300216s46f5698bydac39606354f080e@mail.gmail.com> (raw)
In-Reply-To: <op.us6y25squcb9g9@home-5db3af48a>
On Thu, Apr 30, 2009 at 1:55 AM, Alexander Sorockin <sorockin@yandex.ru> wrote:
> Hmm. It's interesting that sparse itself doesn't seem to compile with
> anything other that gcc. Does that mean that most other compilers are
> "non-standard"?
Sparse use some C99 feature. Those "non-standard" compiler without C99
support can't compiling it. I don't think sparse has much gcc specific
stuff though.
Chris
prev parent reply other threads:[~2009-04-30 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 20:53 `char * s = "abc";' causes compile to crash with a segfault Alexander Sorockin
2009-04-29 21:08 ` Jeff Garzik
2009-04-29 22:43 ` David Given
2009-04-29 23:41 ` Christopher Li
2009-04-30 10:13 ` David Given
2009-04-30 8:55 ` Alexander Sorockin
2009-04-30 9:16 ` Christopher Li [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=70318cbf0904300216s46f5698bydac39606354f080e@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sorockin@yandex.ru \
/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).