From: "Christopher Li" <sparse@chrisli.org>
To: Alexey Dobriyan <adobriyan@sw.ru>
Cc: linux-sparse@vger.kernel.org, adobriyan@gmail.com
Subject: Re: segfaults in pathological cases from gcc testsuite
Date: Mon, 22 Oct 2007 09:38:51 -0700 [thread overview]
Message-ID: <70318cbf0710220938l2ee6195cu85effcbc8f0e99c9@mail.gmail.com> (raw)
In-Reply-To: <20071022152459.GE6271@localhost.sw.ru>
On 10/22/07, Alexey Dobriyan <adobriyan@sw.ru> wrote:
> FWIW, I fed full gcc tree to sparse not only testsuite. Suprisingly it
> crashed only in two places:
>
>
> --------------------------------------------------------
> gcc/testsuite/gcc.c-torture/compile/limits-exprparen.c
I can't reproduce it for me. What command line
are you using?
> --------------------------------------------------------
> gcc/testsuite/gcc.c-torture/compile/limits-caselabels.c
>
This is cause by too deep recursive label statement chain.
Let me see what I can do about it.
Chris
next prev parent reply other threads:[~2007-10-22 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 15:24 segfaults in pathological cases from gcc testsuite Alexey Dobriyan
2007-10-22 16:38 ` Christopher Li [this message]
2007-10-27 22:01 ` Alexey Dobriyan
2007-10-30 23:24 ` [PATCH] " Chris 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=70318cbf0710220938l2ee6195cu85effcbc8f0e99c9@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=adobriyan@gmail.com \
--cc=adobriyan@sw.ru \
--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).