public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112937] New: [14 Regression] GCN: FAILs due to unconditional 'f->use_flat_addressing = true;'
Date: Sat, 09 Dec 2023 11:24:14 +0000	[thread overview]
Message-ID: <bug-112937-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 112937
           Summary: [14 Regression] GCN: FAILs due to unconditional
                    'f->use_flat_addressing = true;'
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: testsuite-fail
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tschwinge at gcc dot gnu.org
                CC: ams at gcc dot gnu.org, jules at gcc dot gnu.org
  Target Milestone: ---
            Target: GCN

The unconditional GCN 'f->use_flat_addressing = true;' applied as part of
commit r14-6226-ge7d6c277fa28c0b9b621d23c471e0388d2912644 "amdgcn, libgomp:
low-latency allocator" is causing a few regressions for GCN target (not
offloading) testing (tested '-march=gfx906', '-march=gfx90a'):

C:

    [-PASS:-]{+FAIL:+} gcc.dg/pr64935-1.c (test for excess errors)

    xgcc: error: [...]/gcc.dg/pr64935-1.c: '-fcompare-debug' failure (length)

Fortran:

    PASS: gfortran.dg/coarray/fail_image_2.f08 -fcoarray=single  -O2  (test for
excess errors)
    [-PASS:-]{+FAIL:+} gfortran.dg/coarray/fail_image_2.f08 -fcoarray=single 
-O2  execution test

    PASS: gfortran.dg/team_change_1.f90   -O0  (test for excess errors)
    [-PASS:-]{+FAIL:+} gfortran.dg/team_change_1.f90   -O0  execution test
    [Etc.]

    PASS: gfortran.dg/team_end_1.f90   -O0  (test for excess errors)
    [-PASS:-]{+FAIL:+} gfortran.dg/team_end_1.f90   -O0  execution test
    [Etc.]

    PASS: gfortran.dg/team_form_1.f90   -O0  (test for excess errors)
    [-PASS:-]{+FAIL:+} gfortran.dg/team_form_1.f90   -O0  execution test
    [Etc.]

    PASS: gfortran.dg/team_number_1.f90   -O0  (test for excess errors)
    [-PASS:-]{+FAIL:+} gfortran.dg/team_number_1.f90   -O0  execution test
    [Etc.]

These execution test FAILs are generally of the form:

    Memory access fault by GPU node-2 (Agent handle: 0x20a1d40) on address
0x7f5600000000. Reason: Page not present or supervisor privilege.

Additionally, I'm seeing the following in my libstdc++ enablement tree:

    PASS: std/ranges/iota/max_size_type.cc  -std=gnu++20 (test for excess
errors)
    {+WARNING: std/ranges/iota/max_size_type.cc  -std=gnu++20 execution test
program timed out.+}
    [-PASS:-]{+FAIL:+} std/ranges/iota/max_size_type.cc  -std=gnu++20 execution
test
    PASS: std/ranges/iota/max_size_type.cc  -std=gnu++26 (test for excess
errors)
    {+WARNING: std/ranges/iota/max_size_type.cc  -std=gnu++26 execution test
program timed out.+}
    [-PASS:-]{+FAIL:+} std/ranges/iota/max_size_type.cc  -std=gnu++26 execution
test

(I guess I could provide pre-processed files for those if you'd like to
reproduce.)

To restore the Fortran test cases, just reverting the GCN back end change is
not sufficient: also need to rebuild GCN target libraries.  (That is, the GCN
back end change does affect code generated for GCN target libraries.)

             reply	other threads:[~2023-12-09 11:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-09 11:24 tschwinge at gcc dot gnu.org [this message]
2023-12-11  9:55 ` [Bug target/112937] " rguenth at gcc dot gnu.org
2023-12-11 15:36 ` tschwinge at gcc dot gnu.org
2023-12-11 15:47 ` ams at gcc dot gnu.org
2024-01-08 15:05 ` tschwinge at gcc dot gnu.org
2024-03-07 20:59 ` law at gcc dot gnu.org
2024-05-07  7:43 ` [Bug target/112937] [14/15 " 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-112937-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).