From: gdb-buildbot@sergiodj.net
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Breakage on builder Ubuntu-Aarch64-m64, revision 90af06793e9d391c0aa33994f21bba6971d084f7
Date: Wed, 05 Dec 2018 16:53:00 -0000 [thread overview]
Message-ID: <E1gUaPw-0006DR-PK@kwanyin.sergiodj.net> (raw)
In-Reply-To: <90af06793e9d391c0aa33994f21bba6971d084f7-master-breakage@gdb-build>
Unfortunately it seems that there is a breakage on GDB.
Commit title: 'gdb/riscv: Improve logic for when h/w float abi should be used'
Revision: 90af06793e9d391c0aa33994f21bba6971d084f7
You can find more details below:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Buildslave:
ubuntu16-aarch64
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Ubuntu-Aarch64-m64/builds/4675>
Commit(s) tested:
90af06793e9d391c0aa33994f21bba6971d084f7
Author(s) (in the same order as the commits):
Andrew Burgess <andrew.burgess@embecosm.com>
Subject:
gdb/riscv: Improve logic for when h/w float abi should be used
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Ubuntu-Aarch64-m64/90/90af06793e9d391c0aa33994f21bba6971d084f7/>
*** Failed to compiled GDB. ***
============================
+++ The full log is too big to be posted here.
+++ These are the last 100 lines of it.
CXX python/py-instruction.o
CXX python/py-lazy-string.o
CXX python/py-linetable.o
CXX python/py-newobjfileevent.o
CXX python/py-objfile.o
CXX python/py-param.o
CXX python/py-prettyprint.o
CXX python/py-progspace.o
CXX python/py-record-btrace.o
CXX python/py-record-full.o
CXX python/py-record.o
CXX python/py-signalevent.o
CXX python/py-stopevent.o
CXX python/py-symbol.o
CXX python/py-symtab.o
CXX python/py-threadevent.o
CXX python/py-type.o
CXX python/py-unwind.o
CXX python/py-utils.o
CXX python/py-value.o
CXX python/py-varobj.o
CXX python/py-xmethods.o
CXX python/python.o
CXX ravenscar-thread.o
CXX record-btrace.o
CXX record-full.o
CXX record.o
CXX regcache-dump.o
CXX regcache.o
CXX reggroups.o
CXX registry.o
CXX remote-fileio.o
CXX remote-notif.o
CXX remote.o
CXX reverse.o
CXX riscv-fbsd-tdep.o
CXX riscv-linux-tdep.o
CXX riscv-tdep.o
CXX rl78-tdep.o
CXX rs6000-aix-tdep.o
CXX rs6000-lynx178-tdep.o
CXX rs6000-tdep.o
CXX rust-exp.o
CXX rust-lang.o
CXX rx-tdep.o
CXX s12z-tdep.o
CXX s390-linux-tdep.o
CXX s390-tdep.o
CXX score-tdep.o
CXX selftest-arch.o
CXX sentinel-frame.o
CXX ser-base.o
CXX ser-event.o
CXX ser-pipe.o
CXX ser-tcp.o
CXX ser-uds.o
CXX ser-unix.o
CXX serial.o
CXX sh-linux-tdep.o
CXX sh-nbsd-tdep.o
CXX sh-tdep.o
CXX skip.o
CXX sol2-tdep.o
CXX solib-aix.o
CXX solib-darwin.o
CXX solib-dsbt.o
CXX solib-frv.o
CXX solib-spu.o
CXX solib-svr4.o
CXX solib-target.o
CXX solib.o
CXX source.o
CXX sparc-linux-tdep.o
CXX sparc-nbsd-tdep.o
CXX sparc-obsd-tdep.o
CXX sparc-ravenscar-thread.o
CXX sparc-sol2-tdep.o
CXX sparc-tdep.o
CXX sparc64-fbsd-tdep.o
CXX sparc64-linux-tdep.o
CXX sparc64-nbsd-tdep.o
CXX sparc64-obsd-tdep.o
CXX sparc64-sol2-tdep.o
CXX sparc64-tdep.o
CXX spu-multiarch.o
CXX spu-tdep.o
g++: internal compiler error: Segmentation fault (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
Makefile:1632: recipe for target 'sparc64-obsd-tdep.o' failed
make[2]: *** [sparc64-obsd-tdep.o] Error 4
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/gdb_buildbot/ubuntu16-aarch64/ubuntu-aarch64-m64/build/gdb'
Makefile:8792: recipe for target 'all-gdb' failed
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory '/home/gdb_buildbot/ubuntu16-aarch64/ubuntu-aarch64-m64/build'
Makefile:849: recipe for target 'all' failed
make: *** [all] Error 2
============================
prev parent reply other threads:[~2018-12-05 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 16:53 Oh dear. I regret to inform you that commit 90af06793e9d391c0aa33994f21bba6971d084f7 might be unfortunate gdb-buildbot
2018-12-05 16:53 ` 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=E1gUaPw-0006DR-PK@kwanyin.sergiodj.net \
--to=gdb-buildbot@sergiodj.net \
--cc=andrew.burgess@embecosm.com \
--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