From: Thomas Schwinge <thomas@codesourcery.com>
To: <gcc-patches@gcc.gnu.org>, <tdevries@suse.de>
Subject: nvptx: Re-enable a number of test cases
Date: Fri, 2 Dec 2022 13:03:06 +0100 [thread overview]
Message-ID: <20221202120315.803120-1-thomas@codesourcery.com> (raw)
Hi!
I'm proposing to re-enable a number of test cases for nvptx. OK to push?
Grüße
Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next reply other threads:[~2022-12-02 12:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 12:03 Thomas Schwinge [this message]
2022-12-02 12:03 ` [PATCH 1/9] nvptx: Re-enable 'gcc.c-torture/compile/20080721-1.c' Thomas Schwinge
2022-12-02 12:03 ` [PATCH 2/9] nvptx: Re-enable "ptxas times out" test cases Thomas Schwinge
2022-12-02 12:03 ` [PATCH 3/9] nvptx: Re-enable test cases by removing effective target 'freestanding' Thomas Schwinge
2022-12-02 12:03 ` [PATCH 4/9] nvptx: Re-enable all variants of 'gcc.c-torture/execute/20020529-1.c' Thomas Schwinge
2022-12-02 12:03 ` [PATCH 5/9] nvptx: Re-enable 'gcc.dg/special/weak-2.c' Thomas Schwinge
2022-12-02 12:03 ` [PATCH 6/9] nvptx: Re-enable all variants of 'c-c++-common/torture/complex-sign-mixed-add.c', 'c-c++-common/torture/complex-sign-mixed-sub.c' Thomas Schwinge
2022-12-02 12:03 ` [PATCH 7/9] nvptx: Re-enable 'gcc.dg/torture/c99-contract-1.c' Thomas Schwinge
2022-12-02 12:03 ` [PATCH 8/9] nvptx: Re-enable "Stack alignment causes use of alloca" test cases Thomas Schwinge
2022-12-02 12:03 ` [PATCH 9/9] nvptx: Re-enable 'gcc.misc-tests/options.exp' Thomas Schwinge
2022-12-20 7:56 ` [PING] nvptx: Re-enable a number of test cases Thomas Schwinge
2023-01-11 11:34 ` [PING^2] " Thomas Schwinge
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=20221202120315.803120-1-thomas@codesourcery.com \
--to=thomas@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tdevries@suse.de \
/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).