public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andre Simoes Dias Vieira <avieira@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-9065] Fix testism where __seg_gs was being used for all targets
Date: Mon, 19 Feb 2024 16:13:19 +0000 (GMT)	[thread overview]
Message-ID: <20240219161319.21F423858D20@sourceware.org> (raw)

https://gcc.gnu.org/g:b29f20b6e271b7cd1faad1ced9a55d92d00fcbfe

commit r14-9065-gb29f20b6e271b7cd1faad1ced9a55d92d00fcbfe
Author: Andre Simoes Dias Vieira <andre.simoesdiasvieira@arm.com>
Date:   Mon Feb 19 15:50:37 2024 +0000

    Fix testism where __seg_gs was being used for all targets
    
    Replaced uses of __seg_gs with the MACRO SEG defined in the testcase to pick
    (if any) the right __seg_{gs,fs} keyword based on target.
    
    gcc/testsuite/ChangeLog:
    
            * gcc.dg/bitint-86.c (__seg_gs): Replace with SEG MACRO.

Diff:
---
 gcc/testsuite/gcc.dg/bitint-86.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/bitint-86.c b/gcc/testsuite/gcc.dg/bitint-86.c
index 4e5761a203bc..10a2392b6f53 100644
--- a/gcc/testsuite/gcc.dg/bitint-86.c
+++ b/gcc/testsuite/gcc.dg/bitint-86.c
@@ -15,14 +15,14 @@ struct T { struct S b[4]; };
 #endif
 
 void
-foo (__seg_gs struct T *p)
+foo (SEG struct T *p)
 {
   struct S s;
   p->b[0] = s;
 }
 
 void
-bar (__seg_gs struct T *p, _BitInt(710) x, int y, double z)
+bar (SEG struct T *p, _BitInt(710) x, int y, double z)
 {
   p->b[0].a = x + 42;
   p->b[1].a = x << y;
@@ -31,7 +31,7 @@ bar (__seg_gs struct T *p, _BitInt(710) x, int y, double z)
 }
 
 int
-baz (__seg_gs struct T *p, _BitInt(710) x, _BitInt(710) y)
+baz (SEG struct T *p, _BitInt(710) x, _BitInt(710) y)
 {
   return __builtin_add_overflow (x, y, &p->b[1].a);
 }

                 reply	other threads:[~2024-02-19 16:13 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=20240219161319.21F423858D20@sourceware.org \
    --to=avieira@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).