public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-6846] testsuite: Fix up gcc.target/i386/pr109137.c testcase [PR109137]
Date: Fri, 24 Mar 2023 08:45:07 +0000 (GMT)	[thread overview]
Message-ID: <20230324084507.9B13E3858CDA@sourceware.org> (raw)

https://gcc.gnu.org/g:0d9e52675c009139a14182d92ddb446ba2feabce

commit r13-6846-g0d9e52675c009139a14182d92ddb446ba2feabce
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Mar 24 09:42:18 2023 +0100

    testsuite: Fix up gcc.target/i386/pr109137.c testcase [PR109137]
    
    The testcase has a couple of small problems:
    1) had -m32 in dg-options, that should never be done, instead the test
       should be guarded on ia32
    2) adds -fPIC unconditionally (that should be guarded on fpic effective
       target)
    3) using #include <string.h> for a RA test seems unnecessary, __builtin_memset
       handles it without the header
    
    2023-03-24  Jakub Jelinek  <jakub@redhat.com>
    
            PR target/109137
            * gcc.target/i386/pr109137.c: Remove -m32 from dg-options, instead
            require ia32 effective target.  Only add -fPIC for fpic effective
            target.  Remove #include <string.h>, use __builtin_memset instead of
            memset.

Diff:
---
 gcc/testsuite/gcc.target/i386/pr109137.c | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/gcc/testsuite/gcc.target/i386/pr109137.c b/gcc/testsuite/gcc.target/i386/pr109137.c
index ffd8e8c574b..e92a5e47855 100644
--- a/gcc/testsuite/gcc.target/i386/pr109137.c
+++ b/gcc/testsuite/gcc.target/i386/pr109137.c
@@ -1,6 +1,8 @@
-/* { dg-do compile } */
-/* { dg-options "-m32 -O3 -march=znver1 -fPIC -mfpmath=sse -w" } */
-#include <string.h>
+/* PR target/109137 */
+/* { dg-do compile { target ia32 } } */
+/* { dg-options "-O3 -march=znver1 -mfpmath=sse -w" } */
+/* { dg-additional-options "-fPIC" { target fpic } } */
+
 typedef struct {
   char bytestream_end;
 } CABACContext;
@@ -12,7 +14,7 @@ typedef struct {
 } H264SliceContext;
 H264SliceContext ff_h264_decode_mb_cabac_sl;
 void ff_h264_decode_mb_cabac(void) {
-  memset((void*)ff_h264_decode_mb_cabac_h_0, 6, 48);
+  __builtin_memset((void*)ff_h264_decode_mb_cabac_h_0, 6, 48);
   int i;
   for (;; i++) {
     __asm__(""/* { dg-error "'asm' operand has impossible constraints" } */
@@ -25,4 +27,3 @@ void ff_h264_decode_mb_cabac(void) {
         decode_cabac_mb_intra4x4_pred_mode_mode;
   }
 }
-

                 reply	other threads:[~2023-03-24  8:45 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=20230324084507.9B13E3858CDA@sourceware.org \
    --to=jakub@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: link
Be 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).