From: Jeff Law <law@redhat.com>
To: Bernd Schmidt <bernds@codesourcery.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [0/6] nvptx testsuite patches
Date: Tue, 21 Oct 2014 14:48:00 -0000 [thread overview]
Message-ID: <544671D3.9050605@redhat.com> (raw)
In-Reply-To: <5446694A.1010705@codesourcery.com>
On 10/21/14 14:10, Bernd Schmidt wrote:
> This series modifies a large number of tests in order to clean up
> testsuite results on nvptx. The goal here was never really to get an
> entirely clean run - the target is just too different from conventional
> ones - but to be able to test the compiler sufficiently to be sure that
> it's in good shape for use in offloading. Most of the patches here add
> annotations for use of features like alloca or indirect jumps that are
> unsupported on the target.
>
> Examples of things that still cause failures are things like dots in
> identifiers, use of constructors (which is something I want to look
> into), certain constructs that trigger bugs in the ptxas tool, and lots
> of undefined C library functions.
Yea. When I first looked at PTX, my thought was to use the existing
testsuite, to the extent possible, to shake out the initial code
generation issues. There's just some things that would require heroic
effort to make work and they aren't really a priority for PTX.
So I've got not problem conceptually with the direction this work is taking.
jeff
prev parent reply other threads:[~2014-10-21 14:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 14:13 Bernd Schmidt
2014-10-21 14:13 ` [1/6] nvptx testsuite patches: alloca Bernd Schmidt
2014-10-21 15:16 ` Jeff Law
2014-10-21 14:19 ` [2/6] nvptx testsuite patches: typed assembly Bernd Schmidt
2014-10-21 15:22 ` Jeff Law
2014-10-21 15:33 ` Bernd Schmidt
2014-11-10 16:23 ` Bernd Schmidt
2014-10-21 14:19 ` [3/6] nvptx testsuite patches: stdio Bernd Schmidt
2014-10-21 15:24 ` Jeff Law
2014-10-21 19:28 ` Mike Stump
2014-10-21 21:11 ` Bernd Schmidt
2014-10-21 14:22 ` [4/6] nvptx testsuite patches: xfails and skips Bernd Schmidt
2014-10-21 15:30 ` Jeff Law
2014-10-21 15:32 ` Bernd Schmidt
2014-10-21 14:27 ` [5/6] nvptx testsuite patches: jumps and labels Bernd Schmidt
2014-10-21 15:31 ` Jeff Law
2014-10-21 14:30 ` [6/7] Random tweaks Bernd Schmidt
2014-10-21 15:33 ` Jeff Law
2014-10-21 17:04 ` Jakub Jelinek
2014-10-21 17:49 ` Marek Polacek
2014-10-21 20:24 ` Mike Stump
2014-10-21 14:34 ` [7/7] nvptx testsuite patches: Return addresses Bernd Schmidt
2014-10-21 15:34 ` Jeff Law
2014-11-10 20:21 ` H.J. Lu
2014-11-10 20:33 ` Mike Stump
2014-11-11 11:58 ` Bernd Schmidt
2014-10-21 14:48 ` Jeff Law [this message]
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=544671D3.9050605@redhat.com \
--to=law@redhat.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@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).