Due to pr64625 I have looked more carefully to your logs and I did not see any
entry for libgomp.
Is it expected?
TIA
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
> appear directly on gcc-testres
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
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 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
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
> 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
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
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 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
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
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
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 darwin
(PIC-related, in particular!).
The hardware is new, t
12 matches
Mail list logo
