public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104200] New: [12 Regression] FAIL: gcc.target/aarch64/atomic-inst-cas.c (test for excess errors) fails
Date: Mon, 24 Jan 2022 09:28:20 +0000	[thread overview]
Message-ID: <bug-104200-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104200

            Bug ID: 104200
           Summary: [12 Regression] FAIL:
                    gcc.target/aarch64/atomic-inst-cas.c (test for excess
                    errors) fails
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: testsuite-fail
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---
            Target: aarch64

+FAIL: gcc.target/aarch64/atomic-inst-cas.c (test for excess errors)
/home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/testsuite/gcc.target/aarch64/atomic-inst-cas.c:
In function 'test_cas_atomic_relaxed_consume_char':^M
/home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/testsuite/gcc.target/aarch64/atomic-inst-cas.c:22:12:
warning: failure memory model 'memory_order_consume' cannot be stronger than
success memory model 'memory_order_relaxed' for '__atomic_compare_exchange_1'
[-Winvalid-memory-model]^M
....

Most likely caused by r12-6216.

             reply	other threads:[~2022-01-24  9:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24  9:28 pinskia at gcc dot gnu.org [this message]
2022-01-24  9:28 ` [Bug target/104200] " pinskia at gcc dot gnu.org
2022-01-27 22:51 ` [Bug testsuite/104200] " pinskia at gcc dot gnu.org
2022-01-27 23:34 ` [Bug tree-optimization/104200] " pinskia at gcc dot gnu.org
2022-01-27 23:42 ` pinskia at gcc dot gnu.org
2022-01-28  0:01 ` pinskia at gcc dot gnu.org
2022-02-16 17:38 ` pinskia at gcc dot gnu.org
2022-05-06  8:32 ` [Bug tree-optimization/104200] [12/13 " jakub at gcc dot gnu.org
2022-07-26 13:03 ` rguenth at gcc dot gnu.org
2023-05-08 12:23 ` [Bug tree-optimization/104200] [12/13/14 " rguenth at gcc dot gnu.org

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=bug-104200-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).