public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Fix Rust testing
Date: Wed, 24 Apr 2019 20:48:00 -0000	[thread overview]
Message-ID: <1670072efb31e82d52d408940062860e2835d79c@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 1670072efb31e82d52d408940062860e2835d79c ***

Author: Tom Tromey <tromey@adacore.com>
Branch: master
Commit: 1670072efb31e82d52d408940062860e2835d79c

Fix Rust testing

This changes the gdb test suite to omit -fno-stack-protector when
compiling Rust code.  This makes Rust testing work again.

I think I saw this patch somewhere already, but I couldn't find it
again just now, so I'm checking this version in.

gdb/testsuite/ChangeLog
2019-04-24  Tom Tromey  <tromey@adacore.com>

	* lib/gdb.exp (gdb_compile): Don't add -fno-stack-protector for
	Rust.


             reply	other threads:[~2019-04-24 20:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 20:48 sergiodj+buildbot [this message]
2019-04-24 21:29 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2019-04-26 17:19 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2019-04-26 18:06 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2019-04-30 13:29 ` Failures on Fedora-i686, " sergiodj+buildbot
2019-04-30 13:50 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2019-04-30 14:01 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2019-04-30 14:07 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2019-04-30 14:39 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2019-05-04 19:20 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot

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=1670072efb31e82d52d408940062860e2835d79c@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).