From: Christopher Li <sparse@chrisli.org>
To: David Given <dg@cowlark.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: `char * s = "abc";' causes compile to crash with a segfault
Date: Wed, 29 Apr 2009 16:41:05 -0700 [thread overview]
Message-ID: <70318cbf0904291641w30f19372ne95e98d1030964cf@mail.gmail.com> (raw)
In-Reply-To: <49F8D803.6080000@cowlark.com>
On Wed, Apr 29, 2009 at 3:43 PM, David Given <dg@cowlark.com> wrote:
>
> In addition, I found a number of places where minor tweaks to what data
> Sparse keeps around can make a compiler writer's life much easier; for
> example, keeping more type data makes finding the type of a pseudo much
> easier. There's a combined patch shipped with Clue that fixes and
> enhances a bunch of this stuff:
>
> http://cluecc.svn.sourceforge.net/viewvc/cluecc/clue/sparse.patch?revision=34&view=markup
I think some of your patch already went into sparse. If there are some
missing. Feel free to submit it again.
> (In fact, if you're generating llvm assembly directly, you may find it
> easier just to add a backend to Clue rather than write your own, er,
> middle-end --- a lot of the simplifications Clue does for languages like
> Javascript also apply to llvm bitcode.)
If every back end needs to do those "simplifications", that means sparse
should be fixed to do it right.
> <plug> Did I mention that Clue is now converting C into Java source that
> runs at 40% of compiled C? </plug>
Oh really, Java?
Chris
next prev parent reply other threads:[~2009-04-29 23:41 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 [this message]
2009-04-30 10:13 ` David Given
2009-04-30 8:55 ` Alexander Sorockin
2009-04-30 9:16 ` Christopher Li
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=70318cbf0904291641w30f19372ne95e98d1030964cf@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=dg@cowlark.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 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).