public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Schmidt <bernds@codesourcery.com>
To: Ilya Verbin <iverbin@gmail.com>, Jakub Jelinek <jakub@redhat.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, Richard Biener <rguenther@suse.de>,
	<gcc-patches@gcc.gnu.org>,
	Thomas Schwinge <thomas@codesourcery.com>,
	Kirill Yukhin <kirill.yukhin@gmail.com>,
	Andrey Turetskiy	<andrey.turetskiy@gmail.com>
Subject: Re: [PATCH 4/n] OpenMP 4.0 offloading infrastructure: lto-wrapper
Date: Thu, 09 Oct 2014 12:13:00 -0000	[thread overview]
Message-ID: <54367AB9.9080501@codesourcery.com> (raw)
In-Reply-To: <20141009120738.GA7420@msticlxl57.ims.intel.com>

On 10/09/2014 02:07 PM, Ilya Verbin wrote:
>>> +#ifndef ACCEL_COMPILER
>>>     /* We need to check standard_exec_prefix/just_machine_suffix/specs
>>>        for any override of as, ld and libraries.  */
>>>     specs_file = (char *) alloca (strlen (standard_exec_prefix)
>>>   		       + strlen (just_machine_suffix) + sizeof ("specs"));
>>> -
>>>     strcpy (specs_file, standard_exec_prefix);
>>>     strcat (specs_file, just_machine_suffix);
>>>     strcat (specs_file, "specs");
>>>     if (access (specs_file, R_OK) == 0)
>>>       read_specs (specs_file, true, false);
>>> +#endif
>>
>> Why do you want to disable specs reading for the accel compiler?
>> Then users won't have the possibility to override defaults etc. easily...
>
> Bernd,
> Do you need this ifndef for PTX?  Or I could remove it?

I suspect the paths aren't right. If that can be fixed it should be fine 
to remove the ifdef.


Bernd

  reply	other threads:[~2014-10-09 12:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02 15:15 Ilya Verbin
2014-10-08 10:27 ` Jakub Jelinek
2014-10-09 12:09   ` Ilya Verbin
2014-10-09 12:13     ` Bernd Schmidt [this message]
2014-10-09 20:27     ` Ilya Verbin
2014-10-10  7:13       ` Jakub Jelinek
2014-10-10 16:52         ` Cary Coutant
2014-10-10 17:01           ` Jakub Jelinek
2014-10-10 17:10             ` Cary Coutant
2014-10-13 22:47             ` Ilya Verbin
2014-10-14  9:41               ` Jakub Jelinek
2014-10-15 14:27                 ` Ilya Verbin
2014-10-15 14:46                   ` Jakub Jelinek
2014-10-16 11:18                     ` Ilya Verbin
2014-10-16 11:27                       ` Jakub Jelinek
2014-10-29 10:28                         ` Kirill Yukhin
2014-11-06 13:00                         ` Ilya Verbin
2014-11-12  9:47                           ` Richard Biener
2014-10-15 17:03                 ` Cary Coutant
2015-05-12 16:32 ` Thomas Schwinge
2015-05-12 17:19   ` Bernd Schmidt
2015-10-02 21:28     ` Help the offload gcc driver find the right assembler (was: [PATCH 4/n] OpenMP 4.0 offloading infrastructure: lto-wrapper) Thomas Schwinge
2016-02-19 19:42 ` [PATCH 4/n] OpenMP 4.0 offloading infrastructure: lto-wrapper Thomas Schwinge
2016-02-19 19:51   ` Ilya Verbin

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=54367AB9.9080501@codesourcery.com \
    --to=bernds@codesourcery.com \
    --cc=andrey.turetskiy@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=iverbin@gmail.com \
    --cc=jakub@redhat.com \
    --cc=kirill.yukhin@gmail.com \
    --cc=rguenther@suse.de \
    --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).