public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-1820] jit: fix test-asm failures on i?86 Date: Fri, 25 Jun 2021 23:09:03 +0000 (GMT) [thread overview] Message-ID: <20210625230903.714623857401@sourceware.org> (raw) https://gcc.gnu.org/g:176289e50e3d379b681f8775cdb0230b1e9f50dc commit r12-1820-g176289e50e3d379b681f8775cdb0230b1e9f50dc Author: David Malcolm <dmalcolm@redhat.com> Date: Fri Jun 25 19:07:25 2021 -0400 jit: fix test-asm failures on i?86 On i686, test_i386_basic_asm_4 has: error: inconsistent operand constraints in an 'asm' and test_i386_basic_asm_5 has: /tmp/libgccjit-9FsLie/fake.s:9: Error: bad register name `%rdi' /tmp/libgccjit-9FsLie/fake.s:10: Error: bad register name `%rsi' This is only intended as a smoketest of asm support, so only run it on x86_64. gcc/testsuite/ChangeLog: * jit.dg/test-asm.c: Remove i?86-*-* from target specifier. * jit.dg/test-asm.cc: Likewise. Signed-off-by: David Malcolm <dmalcolm@redhat.com> Diff: --- gcc/testsuite/jit.dg/test-asm.c | 2 +- gcc/testsuite/jit.dg/test-asm.cc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/testsuite/jit.dg/test-asm.c b/gcc/testsuite/jit.dg/test-asm.c index e7777eeb4fe..35a9f9d8605 100644 --- a/gcc/testsuite/jit.dg/test-asm.c +++ b/gcc/testsuite/jit.dg/test-asm.c @@ -1,4 +1,4 @@ -/* { dg-do compile { target i?86-*-* x86_64-*-* } } */ +/* { dg-do compile { target x86_64-*-* } } */ #include <stdlib.h> #include <stdio.h> diff --git a/gcc/testsuite/jit.dg/test-asm.cc b/gcc/testsuite/jit.dg/test-asm.cc index 6f1828060ff..be487e3fb69 100644 --- a/gcc/testsuite/jit.dg/test-asm.cc +++ b/gcc/testsuite/jit.dg/test-asm.cc @@ -1,4 +1,4 @@ -/* { dg-do compile { target i?86-*-* x86_64-*-* } } */ +/* { dg-do compile { target x86_64-*-* } } */ #include "libgccjit++.h"
reply other threads:[~2021-06-25 23:09 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=20210625230903.714623857401@sourceware.org \ --to=dmalcolm@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).