From: Josh Triplett <josh@freedesktop.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [RFC] infinite loop in free_preprocessor_line()
Date: Sun, 03 Jun 2007 15:27:35 -0700 [thread overview]
Message-ID: <46634057.1000709@freedesktop.org> (raw)
In-Reply-To: <20070602215526.GA5710@martell.zuzino.mipt.ru>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
Alexey Dobriyan wrote:
> On Sat, May 26, 2007 at 05:35:26PM -0700, Josh Triplett wrote:
>> Alexey Dobriyan wrote:
>>> While running if-2.c from gcc testsuite sparse goes into infinite loop in
>>> free_preprocessor_line().
>>>
>>> Trimmed down test-case is
>>>
>>> #if 1
>>> #if
>>>
>>> (two lines)
>> Thanks for this fix.
>>
>> Can I get a Signed-off-by for this patch, please?
>
> Sorry, lost email in noise
>
> Patch is Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Thanks. Applied, along with the test case.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2007-06-03 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 0:24 [RFC] infinite loop in free_preprocessor_line() Alexey Dobriyan
2007-05-27 0:35 ` Josh Triplett
2007-06-02 21:55 ` Alexey Dobriyan
2007-06-03 22:27 ` Josh Triplett [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=46634057.1000709@freedesktop.org \
--to=josh@freedesktop.org \
--cc=adobriyan@gmail.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).