This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[PATCH] Remove restriction for remote testing
- From: James Norris <jnorris at codesourcery dot com>
- To: <gcc-patches at gcc dot gnu dot org>
- Cc: <mikestump at comcast dot net>
- Date: Mon, 28 Sep 2015 07:35:59 -0500
- Subject: [PATCH] Remove restriction for remote testing
- Authentication-results: sourceware.org; auth=none
Hi,
The attached patch fixes a problem when doing remote testing.
Specifically, testing of the atomic tests found in gcc/atomic.
The code in atomic_init precludes the setting of the variable
'link_flags' when doing remote testing. The conditional test
can be safely removed as get_multilibs will return "", and
atomic_link_flags will return the necessary '-latomic' that
will allow the atomic tests to successfully link.
OK for trunk?
Thanks,
Jim
Index: gcc/testsuite/lib/atomic-dg.exp
===================================================================
--- gcc/testsuite/lib/atomic-dg.exp (revision 227981)
+++ gcc/testsuite/lib/atomic-dg.exp (working copy)
@@ -63,12 +63,10 @@ proc atomic_init { args } {
global atomic_saved_TEST_ALWAYS_FLAGS
set link_flags ""
- if ![is_remote host] {
- if [info exists TOOL_OPTIONS] {
- set link_flags "[atomic_link_flags [get_multilibs ${TOOL_OPTIONS}]]"
- } else {
- set link_flags "[atomic_link_flags [get_multilibs]]"
- }
+ if [info exists TOOL_OPTIONS] {
+ set link_flags "[atomic_link_flags [get_multilibs ${TOOL_OPTIONS}]]"
+ } else {
+ set link_flags "[atomic_link_flags [get_multilibs]]"
}
if [info exists TEST_ALWAYS_FLAGS] {