From: Al Viro <viro@ftp.linux.org.uk>
To: Josh Triplett <josh@freedesktop.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Test that causes sparse to hang
Date: Wed, 16 May 2007 08:17:16 +0100 [thread overview]
Message-ID: <20070516071716.GJ4095@ftp.linux.org.uk> (raw)
In-Reply-To: <464AAEA0.9020300@freedesktop.org>
On Wed, May 16, 2007 at 12:11:28AM -0700, Josh Triplett wrote:
> While poking at the GCC testsuite, I found a source file that hangs Sparse. I
> cut it down to the following minimal test case:
>
> #if L'\x1234' != 0x1234
> #endif
> #if ''
> #endif
>
> Documenting this on-list in case someone wants to look at it before I can get
> to it later.
No wide characters, so don't expect the identical behaviour... Shouldn't
hang, obviously. BTW, I wouldn't be too surprised if wide chars blow not
only in preprocessor.
prev parent reply other threads:[~2007-05-16 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 7:11 Test that causes sparse to hang Josh Triplett
2007-05-16 7:17 ` Al Viro [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=20070516071716.GJ4095@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=josh@freedesktop.org \
--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