public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/113448] libgomp.c/alloc-pinned-1.c etc. XPASS
Date: Mon, 12 Feb 2024 13:45:09 +0000	[thread overview]
Message-ID: <bug-113448-4-exnRgh7pnX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113448-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Rainer Orth <ro@gcc.gnu.org>:

https://gcc.gnu.org/g:1e94648ab7b370c5867e146c7f59603e2e6ba2e6

commit r14-8930-g1e94648ab7b370c5867e146c7f59603e2e6ba2e6
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date:   Mon Feb 12 14:44:17 2024 +0100

    libgomp: testsuite: Don't XPASS libgomp.c/alloc-pinned-1.c etc. on
non-Linux targets [PR113448]

    Two libgomp tests XPASS on Solaris (any non-Linux target actually) since
    their introduction:

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

    The problem is that the test just prints

    OS unsupported

    and exits successfully, while the test is XFAILed:

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

    Fixed by aborting immediately after the message above in the non-Linux
    case.

    Tested on i386-pc-solaris2.11 and i686-pc-linux-gnu.

    2024-02-02  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>

            libgomp:
            PR testsuite/113448
            * testsuite/libgomp.c/alloc-pinned-1.c [!__linux__] (CHECK_SIZE):
            Call abort.
            * testsuite/libgomp.c/alloc-pinned-2.c [!__linux__] (CHECK_SIZE):
            Likewise.

  parent reply	other threads:[~2024-02-12 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 15:04 [Bug libgomp/113448] New: " ro at gcc dot gnu.org
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 [this message]
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-exnRgh7pnX@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).