From: rjones@redhat.com (Richard W.M. Jones)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Build failure on ppc64le: Failure("dump: impossible tag (1002)")
Date: Wed, 13 Jan 2016 14:23:04 +0000 [thread overview]
Message-ID: <20160113142304.GL1766@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1601131516180.5214@hadrien>
On Wed, Jan 13, 2016 at 03:17:36PM +0100, Julia Lawall wrote:
>
>
> On Wed, 13 Jan 2016, Richard W.M. Jones wrote:
>
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1297855
> > Build log:
> > http://ppc.koji.fedoraproject.org/kojifiles/work/tasks/345/3060345/build.log
> >
> > In brief the build fails at:
> >
> > + /builddir/build/BUILDROOT/coccinelle-1.0.4-2.fc24.ppc64le/usr/bin/spatch -sp_file demos/simple.cocci demos/simple.c
> > init_defs_builtins: /builddir/build/BUILDROOT/coccinelle-1.0.4-2.fc24.ppc64le/usr/lib64/coccinelle/standard.h
> > Fatal error: exception Failure("dump: impossible tag (1002)")
> >
> > When thinking about this bug, don't exclude the possibility that there
> > could be a problem in the OCaml compiler. In Fedora we currently use
> > a non-upstream ppc64le code generator, although we are planning to
> > replace it soon(-ish) with the new upstream POWER code generator that
> > Xavier wrote last year.
>
> It is actually your code that is crashing :)
>
> (* Dump an OCaml value into a printable string.
> * By Richard W.M. Jones (rich at annexia.org).
> * dumper.ml 1.2 2005/02/06 12:38:21 rich Exp
> *)
>
> Maybe you could send the output of man Obj in your version of Ocaml?
Not sure I understand - we don't change the Obj man page at all.
The implementation of OCaml objects (as in the object header and so
on) should also be the same, AFAIK. Certainly the ppc64le backend
doesn't make any changes inside the OCaml compiler core, eg. to the GC
or libraries. It's a 64 bit LE platform, so AFAIK the memory
structures ought to be identical to x86-64.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
next prev parent reply other threads:[~2016-01-13 14:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 13:48 [Cocci] Build failure on ppc64le: Failure("dump: impossible tag (1002)") Richard W.M. Jones
2016-01-13 14:15 ` Julia Lawall
2016-01-13 14:17 ` Julia Lawall
2016-01-13 14:23 ` Richard W.M. Jones [this message]
2016-01-13 14:26 ` Julia Lawall
2016-01-13 14:30 ` Richard W.M. Jones
2016-01-13 16:02 ` Julia Lawall
2016-01-14 10:28 ` Richard W.M. Jones
2016-01-13 14:23 ` Richard W.M. Jones
2016-01-13 14:54 ` SF Markus Elfring
2016-01-13 15:01 ` Richard W.M. Jones
2016-01-13 15:10 ` Julia Lawall
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=20160113142304.GL1766@redhat.com \
--to=rjones@redhat.com \
--cc=cocci@systeme.lip6.fr \
/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.