public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/aoliva/heads/testme)] skip testsuite/g++.dg/other/anon5.C on vxworks_kernel targets Date: Fri, 1 Jan 2021 01:29:46 +0000 (GMT) [thread overview] Message-ID: <20210101012946.715853857815@sourceware.org> (raw) https://gcc.gnu.org/g:8417c25350963ac80bb87556cbe0ae4fbee6aa63 commit 8417c25350963ac80bb87556cbe0ae4fbee6aa63 Author: Jerome Lambourg <lambourg@adacore.com> Date: Thu Dec 31 21:37:49 2020 -0300 skip testsuite/g++.dg/other/anon5.C on vxworks_kernel targets The vxworks kernel-mode linking is partial linking, so it cannot detect missing symbols. for gcc/testsuite/ChangeLog * g++.dg/other/anon5.C: Skip on vxworks kernel. Diff: --- gcc/testsuite/g++.dg/other/anon5.C | 3 +++ 1 file changed, 3 insertions(+) diff --git a/gcc/testsuite/g++.dg/other/anon5.C b/gcc/testsuite/g++.dg/other/anon5.C index dadd92ef9e4..09853d4c651 100644 --- a/gcc/testsuite/g++.dg/other/anon5.C +++ b/gcc/testsuite/g++.dg/other/anon5.C @@ -1,6 +1,9 @@ // PR c++/34094 // { dg-do link { target { ! { *-*-darwin* *-*-hpux* *-*-solaris2.* } } } } // { dg-require-effective-target nonpic } +// Skip on vxworks kernel: The link being partial, the linker doesn't see +// the undefined reference +// { dg-skip-if "partial link" { vxworks_kernel } } // { dg-options "-gdwarf-2" } // Ignore additional message on powerpc-ibm-aix // { dg-prune-output "obtain more information" } */
next reply other threads:[~2021-01-01 1:29 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-01 1:29 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2020-12-25 1:46 Alexandre Oliva 2020-12-18 14:47 Alexandre Oliva
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=20210101012946.715853857815@sourceware.org \ --to=aoliva@gcc.gnu.org \ --cc=gcc-cvs@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).