public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-3301] Add MIPS Linux support to gcc.misc-tests/linkage.c (testsuite/51748) Date: Wed, 1 Sep 2021 19:49:16 +0000 (GMT) [thread overview] Message-ID: <20210901194916.C18323857C60@sourceware.org> (raw) https://gcc.gnu.org/g:852fdc23a20d07087b5908b57ae7725f435732d5 commit r12-3301-g852fdc23a20d07087b5908b57ae7725f435732d5 Author: Andrew Pinski <apinski@marvell.com> Date: Wed Sep 1 00:13:51 2021 +0000 Add MIPS Linux support to gcc.misc-tests/linkage.c (testsuite/51748) This adds MIPS Linux support to gcc.misc-tests/linkage.exp. Basically copying what was done for MIPS IRIX and changing the options to be correct. OK? gcc/testsuite/ChangeLog: PR testsuite/51748 * gcc.misc-tests/linkage.exp: Add mips*-linux-* support. Diff: --- gcc/testsuite/gcc.misc-tests/linkage.exp | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/gcc/testsuite/gcc.misc-tests/linkage.exp b/gcc/testsuite/gcc.misc-tests/linkage.exp index afed2b811c9..2cb109e776e 100644 --- a/gcc/testsuite/gcc.misc-tests/linkage.exp +++ b/gcc/testsuite/gcc.misc-tests/linkage.exp @@ -38,6 +38,18 @@ if { [isnative] && ![is_remote host] } then { # Need to ensure ABI for native compiler matches gcc set native_cflags "" + if [istarget "mips*-linux*"] { + set file_string [exec file "linkage-x.o"] + if [ string match "*64*" $file_string ] { + set native_cflags "-mabi=64" + } + if [ string match "*ELF 32*" $file_string ] { + set native_cflags "-mabi=32" + } + if [ string match "*N32*" $file_string ] { + set native_cflags "-mabi=n32" + } + } if [istarget "sparc*-sun-solaris2*"] { set file_string [exec file "linkage-x.o"] if [ string match "*64*" $file_string ] {
reply other threads:[~2021-09-01 19:49 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210901194916.C18323857C60@sourceware.org \ --to=pinskia@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).