public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104725] g++.target/i386/pr35513-1.C etc. FAIL Date: Tue, 01 Mar 2022 14:15:54 +0000 [thread overview] Message-ID: <bug-104725-4-zaNIaywYQ0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104725-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104725 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |WAITING Last reconfirmed| |2022-03-01 --- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> --- It looks like Solaris linker doesn't support -mno-direct-extern-access. Did you try GNU linker? This patch limits tests to Linux: diff --git a/gcc/testsuite/g++.target/i386/pr35513-1.C b/gcc/testsuite/g++.target/i386/pr35513-1.C index daa615662c5..82e63277fd2 100644 --- a/gcc/testsuite/g++.target/i386/pr35513-1.C +++ b/gcc/testsuite/g++.target/i386/pr35513-1.C @@ -1,4 +1,4 @@ -// { dg-do run { target property_1_needed } } +// { dg-do run { target { *-*-linux* && property_1_needed } } } // { dg-options "-O2 -mno-direct-extern-access" } #include <iostream> diff --git a/gcc/testsuite/g++.target/i386/pr35513-2.C b/gcc/testsuite/g++.target/i386/pr35513-2.C index ecccdaeb666..95782b10cf3 100644 --- a/gcc/testsuite/g++.target/i386/pr35513-2.C +++ b/gcc/testsuite/g++.target/i386/pr35513-2.C @@ -1,4 +1,4 @@ -// { dg-do run { target property_1_needed } } +// { dg-do run { target { *-*-linux* && property_1_needed } } } // { dg-options "-O2 -mno-direct-extern-access" } class Foo BTW, does it fail on i686-pc-linux-gnu for you?
next prev parent reply other threads:[~2022-03-01 14:15 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-01 9:29 [Bug target/104725] New: " ro at gcc dot gnu.org 2022-03-01 9:29 ` [Bug target/104725] " ro at gcc dot gnu.org 2022-03-01 14:15 ` hjl.tools at gmail dot com [this message] 2022-03-01 15:07 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-03-01 15:30 ` hjl.tools at gmail dot com 2022-03-01 15:36 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-03-01 15:45 ` cvs-commit at gcc dot gnu.org 2022-03-01 15:50 ` [Bug testsuite/104725] " hjl.tools at gmail dot com
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=bug-104725-4-zaNIaywYQ0@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).