From: Dave Jones <davej@redhat.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Al Viro <viro@ftp.linux.org.uk>, linux-sparse@vger.kernel.org
Subject: Re: sparse segfault on ppc64.
Date: Thu, 22 Mar 2007 12:04:21 -0400 [thread overview]
Message-ID: <20070322160421.GH15364@redhat.com> (raw)
In-Reply-To: <20070322070354.GA22151@chrisli.org>
On Thu, Mar 22, 2007 at 12:03:54AM -0700, Christopher Li wrote:
> On Thu, Mar 22, 2007 at 07:33:44AM +0000, Al Viro wrote:
> > Segfault is new (which version?); the fscking mess in altivec is not, but
> > it (a) doesn't depend on host sparse is ran on; (b) shouldn't lead to
> > segfaults. Altivec extensions are undocumented and fortunately used only
> > in one place in the tree. You should get sparse errors, but it shouldn't
> > die on those.
>
> I think the segfault is likely to cause by my recent change in the parser.
>
> Dave, can you get a backtrace of the segfault? Even better if you can
> give me a small test case which I can reproduce it on x86.
I did battle with our ppc64 buildhost last night to try and coax it
into giving me a coredump, no luck. And as I don't have gcc in that
chroot, I couldn't build it natively. Given this is altivec stuff,
I didn't try building it on x86. At which point I admitted defeat
and turned in for the night ;)
I'll see if I can force it into something buildable on x86 later,
but first I'll see if I can get a useful shell on that buildhost
that I can run gcc & gdb in.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-03-22 16:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 6:36 sparse segfault on ppc64 Dave Jones
2007-03-22 7:33 ` Al Viro
2007-03-22 7:03 ` Christopher Li
2007-03-22 12:59 ` Al Viro
2007-03-22 22:16 ` Christopher Li
2007-03-23 23:08 ` [PATCH] Fix the annotated inline call position Christopher Li
2007-04-20 10:09 ` Josh Triplett
2007-03-22 16:04 ` Dave Jones [this message]
2007-03-22 17:11 ` sparse segfault on ppc64 Dave Jones
2007-03-22 22:10 ` Christopher Li
2007-03-23 22:04 ` more spewage (Re: sparse segfault on ppc64) Randy Dunlap
2007-03-23 22:57 ` Christopher Li
2007-03-23 23:10 ` [PATCH] handle label attributes Christopher Li
2007-03-25 18:52 ` Randy Dunlap
2007-04-20 10:17 ` Josh Triplett
2007-03-23 23:31 ` more spewage (Re: sparse segfault on ppc64) Sam Ravnborg
2007-03-23 23:01 ` Christopher Li
2007-03-23 23:43 ` Randy Dunlap
2007-03-24 6:44 ` Sam Ravnborg
2007-03-24 16:46 ` Randy Dunlap
2007-03-24 17:02 ` Linus Torvalds
2007-03-26 18:07 ` Christopher Li
2007-03-26 18:50 ` Randy Dunlap
2007-03-22 15:56 ` sparse segfault on ppc64 Dave Jones
2007-03-22 16:02 ` Al Viro
2007-03-22 8:36 ` [PATCH] vector parsing, was " Christopher Li
2007-03-23 23:14 ` [PATCH] vector parsing (take II) 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=20070322160421.GH15364@redhat.com \
--to=davej@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=viro@ftp.linux.org.uk \
/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.