linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Given <dg@cowlark.com>
To: linux-sparse@vger.kernel.org
Subject: Re: `char * s = "abc";' causes compile to crash with a segfault
Date: Thu, 30 Apr 2009 11:13:34 +0100	[thread overview]
Message-ID: <49F979CE.5080308@cowlark.com> (raw)
In-Reply-To: <70318cbf0904291641w30f19372ne95e98d1030964cf@mail.gmail.com>

Christopher Li wrote:
[...]
> I think some of your patch already went into sparse. If there are some
> missing. Feel free to submit it again.

The bulk of it's the byte-size patch, which has already made it in, and 
the rest is Clue-specific tweaks (like keeping type information in 
pseudos, and so on).

[...]
> If every back end needs to do those "simplifications", that means sparse
> should be fixed to do it right.

Actually that stuff's in Clue rather than in the patch --- things like 
ultra-simple register allocation, flattening Sparse's parse tree to 
Clue's backend model, etc. None of this really makes sense for anything 
involving a real compiler (for example, Clue assumes you have an 
infinite number of registers available).

In fact, now I think of it, Clue also has a rather intrinsic assumption 
that sizeof(int) == sizeof(char) == 1, which means it wouldn't work with 
llvm out of the box. It may be productive to rip off some of the code, 
though.

-- 
David Given
dg@cowlark.com

  reply	other threads:[~2009-04-30 10:13 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 [this message]
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=49F979CE.5080308@cowlark.com \
    --to=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).