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)] Add missing vxworks filters to lib/target-supports.exp functions Date: Fri, 1 Jan 2021 01:29:21 +0000 (GMT) [thread overview] Message-ID: <20210101012921.116E03857815@sourceware.org> (raw) https://gcc.gnu.org/g:b5183a683f568edb7982df1b5ebc0962725f39c0 commit b5183a683f568edb7982df1b5ebc0962725f39c0 Author: Olivier Hainque <hainque@adacore.com> Date: Thu Dec 31 21:37:42 2020 -0300 Add missing vxworks filters to lib/target-supports.exp functions Explicitly disable some vxworks-missing features in the testsuite, that the current feature tests detect as present. for gcc/testsuite/ChangeLog * lib/target-supports.exp (check_weak_available, check_fork_available, check_effective_target_lto, check_effective_target_mempcpy): Add vxworks filters. Diff: --- gcc/testsuite/lib/target-supports.exp | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp index 11343d0192f..7cad03556c2 100644 --- a/gcc/testsuite/lib/target-supports.exp +++ b/gcc/testsuite/lib/target-supports.exp @@ -326,6 +326,12 @@ proc check_weak_available { } { return 0 } + # VxWorks hardly supports it (vx7 RTPs only) + + if { [istarget *-*-vxworks*] } { + return 0 + } + # ELF and ECOFF support it. a.out does with gas/gld but may also with # other linkers, so we should try it @@ -2606,6 +2612,11 @@ proc check_function_available { function } { # Returns true iff "fork" is available on the target system. proc check_fork_available {} { + if { [istarget *-*-vxworks*] } { + # VxWorks doesn't have fork but our way to test can't + # tell as we're doing partial links for kernel modules. + return 0 + } return [check_function_available "fork"] } @@ -9295,6 +9306,11 @@ proc check_effective_target_gld { } { # (LTO) support. proc check_effective_target_lto { } { + if { [istarget *-*-vxworks*] } { + # No LTO on VxWorks, with kernel modules + # built with partial links + return 0 + } if { [istarget nvptx-*-*] || [istarget amdgcn-*-*] } { return 0; @@ -9514,6 +9530,11 @@ proc check_effective_target_run_expensive_tests { } { # Returns 1 if "mempcpy" is available on the target system. proc check_effective_target_mempcpy {} { + if { [istarget *-*-vxworks*] } { + # VxWorks doesn't have mempcpy but our way to test fails + # to detect as we're doing partial links for kernel modules. + return 0 + } return [check_function_available "mempcpy"] }
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:45 Alexandre Oliva 2020-12-18 14:46 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=20210101012921.116E03857815@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).