On Fri, Feb 20, 2015 at 22:48:52 +0300, Ilya Verbin wrote:
> On Fri, Feb 20, 2015 at 18:05:01 +0300, Ilya Verbin wrote:
> > On Thu, Feb 19, 2015 at 13:17:37 +0100, Thomas Schwinge wrote:
> > > My asumption is that it is always safe to install non-native (that is
> > > cross) GCC installations into
On Fri, Feb 20, 2015 at 18:05:01 +0300, Ilya Verbin wrote:
> On Thu, Feb 19, 2015 at 13:17:37 +0100, Thomas Schwinge wrote:
> > My asumption is that it is always safe to install non-native (that is
> > cross) GCC installations into the same prefix. (Which would resolve this
> > problem of clashing
On Thu, Feb 19, 2015 at 13:17:37 +0100, Thomas Schwinge wrote:
> My asumption is that it is always safe to install non-native (that is
> cross) GCC installations into the same prefix. (Which would resolve this
> problem of clashing file names for target and offloading compilers for
> good.)
>
> S
Hi!
On Thu, 19 Feb 2015 13:08:20 +0100, Bernd Schmidt
wrote:
> On 02/19/2015 12:42 PM, Thomas Schwinge wrote:
> > This specific buglet aside (that the handling of intelmic and nvptx
> > offloading is inconsistent) -- will we have to add such handling to each
> > and every library that is built f
On 02/19/2015 12:42 PM, Thomas Schwinge wrote:
This specific buglet aside (that the handling of intelmic and nvptx
offloading is inconsistent) -- will we have to add such handling to each
and every library that is built for the offloading compilers? (Including
libraries that aren't part of the G
