public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/103244] New: [12 regression] c-c++-common/goacc/firstprivate-mappings-1.c fails on arm since g:b7e20480630e3eeb9eed8b3941da3b3f0c22c969
Date: Mon, 15 Nov 2021 09:36:53 +0000	[thread overview]
Message-ID: <bug-103244-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103244
           Summary: [12 regression]
                    c-c++-common/goacc/firstprivate-mappings-1.c fails on
                    arm since g:b7e20480630e3eeb9eed8b3941da3b3f0c22c969
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: clyon at gcc dot gnu.org
  Target Milestone: ---

I have noticed a failure on arm since
g:b7e20480630e3eeb9eed8b3941da3b3f0c22c969

FAIL: c-c++-common/goacc/firstprivate-mappings-1.c scan-tree-dump omplower
"(?n)#pragma omp target oacc_parallel firstprivate\\(array_li.[0-9]+\\)
map\\(from:array_so \\[len: 4\\]\\) \\["

             reply	other threads:[~2021-11-15  9:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15  9:36 clyon at gcc dot gnu.org [this message]
2021-11-15 11:27 ` [Bug other/103244] " rguenth at gcc dot gnu.org
2021-11-15 11:33 ` [Bug testsuite/103244] " tschwinge at gcc dot gnu.org
2021-11-24 11:00 ` cvs-commit at gcc dot gnu.org
2021-11-24 11:10 ` [Bug testsuite/103244] [12 regression] c-c++-common/goacc/firstprivate-mappings-1.c fails in certain configurations " tschwinge at gcc dot gnu.org
2021-11-25  0:08 ` fche2 at elastic dot 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-103244-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).