From: Jeff Garzik <jeff@garzik.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: Wed, 29 Apr 2009 17:08:59 -0400 [thread overview]
Message-ID: <49F8C1EB.5010909@garzik.org> (raw)
In-Reply-To: <op.us51m0w9ucb9g9@home-5db3af48a>
Alexander Sorockin wrote:
> I realize that compile is only an example and you are probably familiar
> with the problem, but just in case... I was playing around with compile
> and here's what got.
Yes, that is expected behavior for the program merged as "silly sparse
x86 backend" :) There are many, many, many code generator shortcomings.
> Just out of curiosity, is sparse stable enough in general to be used as
> a full-fledged front-end for a C compiler?
As long as you don't do super-weird, non-standard C: sure.
Jeff
next prev parent reply other threads:[~2009-04-29 21:09 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 [this message]
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
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=49F8C1EB.5010909@garzik.org \
--to=jeff@garzik.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.