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 13:48:18 +0000 [thread overview]
Message-ID: <20160113134818.GA30557@redhat.com> (raw)
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.
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 reply other threads:[~2016-01-13 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 13:48 Richard W.M. Jones [this message]
2016-01-13 14:15 ` [Cocci] Build failure on ppc64le: Failure("dump: impossible tag (1002)") Julia Lawall
2016-01-13 14:17 ` Julia Lawall
2016-01-13 14:23 ` Richard W.M. Jones
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=20160113134818.GA30557@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.