Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-patches@sourceware.org
To: gdb-patches@sourceware.org, Barnaby Wilks <barnaby.wilks@arm.com>
To: gdb-patches@sourceware.org, Nick Clifton <nickc@redhat.com>
Subject: Breakage on builder Fedora-i686, revision 236ab0c60c9cedecd4fc23b526a588ee25636c13
Date: Mon, 22 Jul 2019 13:34:00 -0000	[thread overview]
Message-ID: <E1hpYSX-0006hC-Ie@gdb-buildbot.osci.io> (raw)
In-Reply-To: <236ab0c60c9cedecd4fc23b526a588ee25636c13-master-breakage@gdb-build>

Unfortunately it seems that there is a breakage on GDB.

Commit title: 'This patch addresses the change in the June Armv8.1-M Mainline specification, that marks certain MVE instructions as no longer UNPREDICTABLE when a source operand is the same as a destination operand for a 32-bit element size.'
Revision: 236ab0c60c9cedecd4fc23b526a588ee25636c13

You can find more details below:

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


+++ The full log is too big to be posted here.
+++ These are the last 100 lines of it.

  CXX    arch-utils.o
  CXX    arch/aarch32.o
  CXX    arch/arm-get-next-pcs.o
  CXX    arch/arm-linux.o
  CXX    arch/arm.o
  CXX    arch/i386.o
  CXX    arch/ppc-linux-common.o
  CXX    arch/riscv.o
  CXX    arm-bsd-tdep.o
  CXX    arm-fbsd-tdep.o
  CXX    arm-linux-tdep.o
  CXX    arm-nbsd-tdep.o
  CXX    arm-obsd-tdep.o
  CXX    arm-pikeos-tdep.o
  CXX    arm-symbian-tdep.o
  CXX    arm-tdep.o
  CXX    arm-wince-tdep.o
  CXX    auto-load.o
  CXX    auxv.o
  CXX    avr-tdep.o
  CXX    ax-gdb.o
  CXX    ax-general.o
  CXX    bcache.o
  CXX    bfd-target.o
  CXX    bfin-linux-tdep.o
  CXX    bfin-tdep.o
  CXX    block.o
  CXX    blockframe.o
  CXX    break-catch-sig.o
  CXX    break-catch-syscall.o
  CXX    break-catch-throw.o
  CXX    breakpoint.o
  CXX    bsd-uthread.o
  CXX    btrace.o
  CXX    build-id.o
  CXX    buildsym-legacy.o
  CXX    buildsym.o
  CXX    c-exp.o
  CXX    c-lang.o
  CXX    c-typeprint.o
  CXX    c-valprint.o
  CXX    c-varobj.o
  CXX    charset.o
  CXX    cli-out.o
  CXX    cli/cli-cmds.o
  CXX    cli/cli-decode.o
  CXX    cli/cli-dump.o
  CXX    cli/cli-interp.o
  CXX    cli/cli-logging.o
  CXX    cli/cli-option.o
  CXX    cli/cli-script.o
  CXX    cli/cli-setshow.o
  CXX    cli/cli-style.o
  CXX    cli/cli-utils.o
  CXX    coff-pe-read.o
  CXX    coffread.o
  CXX    compile/compile-c-support.o
  CXX    compile/compile-c-symbols.o
  CXX    compile/compile-c-types.o
  CXX    compile/compile-cplus-symbols.o
  CXX    compile/compile-cplus-types.o
  CXX    compile/compile-loc2c.o
  CXX    compile/compile-object-load.o
  CXX    compile/compile-object-run.o
  CXX    compile/compile.o
  CXX    complaints.o
  CXX    completer.o
  CXX    continuations.o
  CXX    copying.o
  CXX    corefile.o
  CXX    corelow.o
  CXX    cp-abi.o
  CXX    cp-name-parser.o
  CXX    cp-namespace.o
  CXX    cp-support.o
  CXX    cp-valprint.o
  CXX    cris-linux-tdep.o
  CXX    cris-tdep.o
  CXX    csky-linux-tdep.o
  CXX    csky-tdep.o
  CXX    ctf.o
  CXX    d-exp.o
  CXX    d-lang.o
  CXX    d-namespace.o
  CXX    d-valprint.o
  CXX    dbxread.o
  CXX    dcache.o
  CXX    debug.o
  CXX    demangle.o
  CXX    dicos-tdep.o
  CXX    dictionary.o
  CXX    disasm-selftests.o
  CXX    disasm.o
  CXX    dtrace-probe.o

command timed out: 1200 seconds without output running [b'make', b'-j4', b'all'], attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=1889.965707


      reply	other threads:[~2019-07-22 13:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 13:34 Oh dear. I regret to inform you that commit 236ab0c60c9cedecd4fc23b526a588ee25636c13 might be unfortunate gdb-buildbot
2019-07-22 13:34 ` gdb-buildbot [this message]

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=E1hpYSX-0006hC-Ie@gdb-buildbot.osci.io \
    --to=gdb-buildbot@sergiodj.net \
    --cc=gdb-patches@sourceware.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