All of lore.kernel.org
 help / color / mirror / Atom feed
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 15:01:33 +0000	[thread overview]
Message-ID: <20160113150133.GO1766@redhat.com> (raw)
In-Reply-To: <5696652C.5080903@users.sourceforge.net>

On Wed, Jan 13, 2016 at 03:54:36PM +0100, SF Markus Elfring wrote:
> > But note I'm not saying this is not a compiler bug.
> > We've had a few.
> 
> Interesting ?
> 
> How do you think about to share any more information
> about the last working system configuration
> for your special build environment?

I'm not sure that it has ever worked on ppc64le.  Looking at our POWER
build systems status:

http://ppc.koji.fedoraproject.org/koji/packageinfo?packageID=919

it looks like it has not built successfully for 3 years, and the last
time it was building that was only on ppc32.

> > Is there a test case you could send me?
> 
> In which kind of test scripts are you interested in?

Anything that would narrow down or potentially reproduce this
particular error, I guess.  Basically if you need me to run any
diagnostic tests, I can.

We also (in partnership with IBM) have a public rack of POWER systems
that anyone can provision (but you have to agree to some legal stuff):

http://research.redhat.com/powerlinux-openpower-development-hosting/

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/

  reply	other threads:[~2016-01-13 15:01 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
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 [this message]
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=20160113150133.GO1766@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.