public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Julian Brown <julian@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org,
	Thomas Schwinge <thomas@codesourcery.com>,
	       Ilya Verbin <iverbin@gmail.com>
Subject: Re: [PATCH 4/5] OpenACC 2.0 support for libgomp - new tests (repost)
Date: Thu, 13 Nov 2014 10:17:00 -0000	[thread overview]
Message-ID: <20141113101518.GG5026@tucnak.redhat.com> (raw)
In-Reply-To: <20141111135442.4284c3de@octopus>

On Tue, Nov 11, 2014 at 01:54:42PM +0000, Julian Brown wrote:
> @@ -169,6 +192,57 @@ proc libgomp_init { args } {
>  
>      # Disable color diagnostics
>      lappend ALWAYS_CFLAGS "additional_flags=-fdiagnostics-color=never"
> +
> +    # TODO.  Evil hack.  DejaGnu doesn't have a mechanism for setting
> +    # environment variables on remote boards.  Thus, we have to fake it, using
> +    # GCC's constructor attributes to create object files that install the
> +    # desired environment variables.

...

Please don't add ugly hacks, I thought Thomas said you didn't mean to put
this in.

> +global shlib_ext
> +
> +set shlib_ext [get_shlib_extension]
> +#TODO

???

> +# Turn on OpenACC.
> +# XXX (TEMPORARY): Remove the -flto once that's properly integrated.
> +lappend ALWAYS_CFLAGS "additional_flags=-fopenacc -flto"

Do you still need that?

> +    # Todo: get list of accelerators from configure options --enable-accelerator.
> +    set accels { "nvidia" "host_nonshm" }

I hope intelmicemul and intelmic will be added here soon.

> +	# Todo: Determine shared memory or not using run-time test.

Please just do that using the run-time test.

	Jakub

  reply	other threads:[~2014-11-13 10:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 18:21 [PATCH 10/10] OpenACC 2.0 support for libgomp - new tests Julian Brown
2014-11-11 13:55 ` [PATCH 4/5] OpenACC 2.0 support for libgomp - new tests (repost) Julian Brown
2014-11-13 10:17   ` Jakub Jelinek [this message]
2014-11-15  6:19     ` Julian Brown
2014-11-17 11:56       ` Julian Brown

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=20141113101518.GG5026@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iverbin@gmail.com \
    --cc=julian@codesourcery.com \
    --cc=thomas@codesourcery.com \
    /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).