public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-3239] Enable support for atomic primitives on SPARC/Linux
Date: Tue, 11 Oct 2022 22:40:25 +0000 (GMT)	[thread overview]
Message-ID: <20221011224025.16A323857361@sourceware.org> (raw)

https://gcc.gnu.org/g:2c328e58c5d7cca10dd404ad8f81ec7664db1fbf

commit r13-3239-g2c328e58c5d7cca10dd404ad8f81ec7664db1fbf
Author: Eric Botcazou <ebotcazou@adacore.com>
Date:   Wed Oct 12 00:38:04 2022 +0200

    Enable support for atomic primitives on SPARC/Linux
    
    The SPARC/Linux port is very similar to the SPARC/Solaris port nowadays so
    it makes sense to copy the setting of the support for atomic primitives.
    
    This fixes the single regression in the gnat.dg testsuite:
    FAIL: gnat.dg/prot7.adb (test for excess errors)
    
    gcc/ada/
            * libgnat/system-linux-sparc.ads (Support_Atomic_Primitives): New
            constant set to True.

Diff:
---
 gcc/ada/libgnat/system-linux-sparc.ads | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/ada/libgnat/system-linux-sparc.ads b/gcc/ada/libgnat/system-linux-sparc.ads
index cc502da3e5b..6d4ee380b2d 100644
--- a/gcc/ada/libgnat/system-linux-sparc.ads
+++ b/gcc/ada/libgnat/system-linux-sparc.ads
@@ -133,6 +133,7 @@ private
    Stack_Check_Probes        : constant Boolean := True;
    Stack_Check_Limits        : constant Boolean := False;
    Support_Aggregates        : constant Boolean := True;
+   Support_Atomic_Primitives : constant Boolean := True;
    Support_Composite_Assign  : constant Boolean := True;
    Support_Composite_Compare : constant Boolean := True;
    Support_Long_Shifts       : constant Boolean := True;

                 reply	other threads:[~2022-10-11 22:40 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=20221011224025.16A323857361@sourceware.org \
    --to=ebotcazou@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).