Mark Farnell wrote:
> Has OpenACC 2.0 support been merged into the trunk yet? If not, then
> is it contained in gomp-4_0-branch?
>
> If so, what parameters should I pass to ./configure to enable OpenACC
> 2.0, and relevant backends such as CUDA, MIC and other GPGPU/manycore
> architecture?
>
> Als
Hi,
On 9 December 2014 at 09:16, Jay Foad wrote:
> I've followed the instructions to request access to the GCC compile
> farm (https://gcc.gnu.org/wiki/CompileFarm#How_to_Get_Involved.3F) but
> heard nothing for two weeks, despite a ping. Are the instructions
> still correct? Is there anyone else
Hi FX,
On 15 Dec 2014, at 21:11, FX wrote:
> Hi all,
>
> I’ve set up daily builds and regtests on a darwin box. The results should
> appear directly on gcc-testresults
> (https://gcc.gnu.org/ml/gcc-testresults/current/).
> This should, in the future, help track down regressions affecting darwi
On Tue, Dec 16, 2014 at 10:13 AM, Jay Foad wrote:
> I've pinged again and waited another week with no response. Is there
> no-one else who can administer compile farm accounts?
Maybe you should try the gcc-cfarm mailing list:
https://mail.gna.org/listinfo/gcc-cfarm-users
It seems very responsive
Hi,
I may have found a bug when I was trying to port my private backend to new LRA
pass (using gcc 4.9.2+patches).
In lra-constraints.c, in function simple_move_p, the target hook
targetm.register_move_cost is called with two badly swapped parameters :
targetm.register_move_cost (GET_M
Richard Biener wrote:
> On Fri, Dec 12, 2014 at 1:08 PM, Ulrich Weigand wrote:
> > Richard Biener wrote:
> >> On Thu, Dec 11, 2014 at 4:04 PM, Ulrich Weigand
> >> wrote:
> >> > However, if we make that change, there will be some cases that regress:
> >> > the
> >> > problem is that an expressio
Hi FX,
Thanks for doing that.
Looking at your results for gcc 5.0, I see a lot of gcc.dg/ubsan/* failures I
don’t see in my tests. Any idea why?
Dominique
> Le 15 déc. 2014 à 22:11, FX a écrit :
>
> Hi all,
>
> I’ve set up daily builds and regtests on a darwin box. The results should
> app
On 16 Dec 2014, at 19:38, Dominique d'Humières wrote:
> Looking at your results for gcc 5.0, I see a lot of gcc.dg/ubsan/* failures I
> don’t see in my tests. Any idea why?
I think that there will be ubsan fails until the library is installed (which
implies that the testing is not setting the
That's good news. Does it mean that if I want to try out openACC with
KNL and PTX support, then all I need to do is to compile the
gomp-4_0-branch *without* any extra parameters into ./configure ?
Also, are other GPUs such as the AMD ATI and the built-in GPUs such as
the Intel GPU and AMD fusion
Is it again the difference between testing before or after install?
Dominique
> Le 16 déc. 2014 à 20:50, Iain Sandoe a écrit :
>
>
> On 16 Dec 2014, at 19:38, Dominique d'Humières wrote:
>
>> Looking at your results for gcc 5.0, I see a lot of gcc.dg/ubsan/* failures
>> I don’t see in my tes
On Wed, Dec 17, 2014 at 08:54:06AM +1300, Mark Farnell wrote:
> That's good news. Does it mean that if I want to try out openACC with
> KNL and PTX support, then all I need to do is to compile the
> gomp-4_0-branch *without* any extra parameters into ./configure ?
No. Please read the wiki page T
Yes, the ubsan issues are about setting DYLD_LIBRARY_PATH:
dyld: Symbol not found: __ZTIN10__cxxabiv117__class_type_infoE
Referenced from:
/Users/fx/autobuilds/builds/gcc-trunk-218778/x86_64-apple-darwin14.0.0/i386/libsanitizer/ubsan/.libs/libubsan.0.dylib
Expected in: /usr/lib/libstdc++.6.dy
> Another testsuite issue on darwin is that testsuite doesn’t clean up the
> .dSYM directories it generates. This gets really annoying on my autotester :(
I have a patch for that, but Iain does not like it!-(
Dominique
On 16 Dec 2014, at 20:40, Dominique d'Humières wrote:
>
>> Another testsuite issue on darwin is that testsuite doesn’t clean up the
>> .dSYM directories it generates. This gets really annoying on my autotester :(
>
> I have a patch for that, but Iain does not like it!-(
Hmm .. I like the patc
On Dec 16, 2014, at 12:46 PM, Iain Sandoe wrote:
>
> On 16 Dec 2014, at 20:40, Dominique d'Humières wrote:
>>
>>> Another testsuite issue on darwin is that testsuite doesn’t clean up the
>>> .dSYM directories it generates. This gets really annoying on my autotester
>>> :(
>>
>> I have a patch
My patch is different and I am attaching it (it is quite old, so it may not
apply cleanly). The problem for more evolved form is that *.dSYM are
directories and ASAICT there is no command in derange to remove them.
At least my patch tracks all the locations giving *.dSYM.
Dominique
patch-dsym
On Dec 16, 2014, at 1:24 PM, Dominique d'Humières wrote:
> My patch is different and I am attaching it (it is quite old, so it may not
> apply cleanly). The problem for more evolved form is that *.dSYM are
> directories and ASAICT there is no command in derange to remove them.
>
> At least my p
So what parameters will I need to pass to ./configure if I want to
support PTX offloading?
So if I want to have CPU, KNL and PTX, do I end up building three compilers?
And is it true that running in both the offload mode, and the KNL
native mode, would require two set of toolchains?
Finally, is
18 matches
Mail list logo
