public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/113448] New: libgomp.c/alloc-pinned-1.c etc. XPASS
Date: Wed, 17 Jan 2024 15:04:08 +0000	[thread overview]
Message-ID: <bug-113448-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113448
           Summary: libgomp.c/alloc-pinned-1.c etc. XPASS
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgomp
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ro at gcc dot gnu.org
                CC: ams at gcc dot gnu.org, jakub at gcc dot gnu.org
  Target Milestone: ---
            Target: *-*-solaris2.11

Two new libgomp testcases introduced in

commit 348874f0baac0f22c98ab11abbfa65fd172f6bdd
Author: Andrew Stubbs <ams@codesourcery.com>
Date:   Tue Jan 4 12:22:01 2022 +0000

    libgomp: basic pinned memory on Linux

XPASS on Solaris/SPARC and x86, 32 and 64-bit:

+XPASS: libgomp.c/alloc-pinned-1.c execution test
+XPASS: libgomp.c/alloc-pinned-2.c execution test

The tests emit

OS unsupported

The XPASSes are no wonder since on any non-Linux target, the tests have

int  
get_pinned_mem ()
{ 
  return 0;
} 

and at the same time

/* { dg-xfail-run-if "Pinning not implemented on this host" { ! *-*-linux-gnu }
} */

However, the test fake-PASSes, thus the XPASS.  I believe get_pinned_mem should
simply abort() on unsupported OSes.

             reply	other threads:[~2024-01-17 15:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 15:04 ro at gcc dot gnu.org [this message]
2024-01-17 15:04 ` [Bug libgomp/113448] " ro at gcc dot gnu.org
2024-01-17 19:28 ` danglin at gcc dot gnu.org
2024-01-20 19:20 ` danglin at gcc dot gnu.org
2024-02-02 14:48 ` seurer at gcc dot gnu.org
2024-02-05 12:59 ` ro at gcc dot gnu.org
2024-02-12 13:45 ` cvs-commit at gcc dot gnu.org
2024-02-12 13:48 ` ro 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-113448-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).