Re: Revert gcc r227962

2016-02-27 Thread JonY
On 2/27/2016 05:26, Jeff Law wrote:
> On 02/26/2016 04:04 AM, JonY wrote:
>> Hi,
>>
>> I've submitted a patch that was committed as r227962, it causes some
>> unintended side effects (namely libuuid on Cygwin). Can someone please
>> revert?
>>
>> Kai still needs some time to setup his gcc development environment.
> We'd need to have a better sense of why this is causing problems.  If
> Kai could chime in with a description of the problem it would be helpful.
> 

Normally, /usr/lib is searched BEFORE /usr/lib/w32api. The patch caused
w32api to be searched before /usr/lib.

libuuid.a is known to exist in both directories, with the *nix version
in /usr/lib and the import library for Windows in w32api. The w32api
copy is completely unrelated to the *nix version. This break cygwin apps
that expect to link against *nix libuuid.




signature.asc
Description: OpenPGP digital signature


Re: [Fortran, Patch] (Coarrays) Wrong events size

2016-02-27 Thread Alessandro Fanfarillo
Thanks!

Patch committed as revision 233779 on trunk and as revision 233780 on
gcc-5-branch.

2016-02-26 19:14 GMT+01:00 Paul Richard Thomas :
> Dear Alessandro,
>
> Seconded! I saw your ping on my phone and was going to respond.
> well, now :-)
>
> Thanks for the patch
>
> Paul
>
> On 26 February 2016 at 18:29, Thomas Koenig  wrote:
>> Hi Allessandro,
>>
>>> * PING *
>>
>>
>> Looks obvious and simple enough for me.
>>
>> OK.
>>
>> Thanks for the patch!
>>
>> Thomas
>>
>
>
>
> --
> The difference between genius and stupidity is; genius has its limits.
>
> Albert Einstein


[committed] Fix up PR69613 and PR69886 testcases

2016-02-27 Thread Jakub Jelinek
Hi!

I've noticed these tests fail on powerpc64*-linux (need -w, otherwise
the backend warns about ABI stuff (should have been probably -Wpsabi
note, but it isn't, and various tests in dg-torture are already using -w),
and one needa avx_runtime.  Fixed thusly, committed as obvious to trunk.

2016-02-27  Jakub Jelinek  

PR target/69613
PR rtl-optimization/69886
* gcc.dg/torture/pr69886.c: Add -w -Wno-psabi to dg-options.
* gcc.dg/torture/pr69613.c: Likewise.  Guard -mavx with avx_runtime
target.

--- gcc/testsuite/gcc.dg/torture/pr69886.c.jj   2016-02-24 14:52:14.0 
+0100
+++ gcc/testsuite/gcc.dg/torture/pr69886.c  2016-02-27 14:25:52.280172085 
+0100
@@ -1,6 +1,6 @@
 /* PR rtl-optimization/69886.  */
 /* { dg-do compile } */
-/* { dg-options "--param=gcse-unrestricted-cost=0" } */
+/* { dg-options "--param=gcse-unrestricted-cost=0 -w -Wno-psabi" } */
 /* { dg-additional-options "-mavx" { target { i?86-*-* x86_64-*-* } } } */
 
 typedef unsigned v32su __attribute__ ((vector_size (32)));
--- gcc/testsuite/gcc.dg/torture/pr69613.c.jj   2016-02-26 20:30:20.0 
+0100
+++ gcc/testsuite/gcc.dg/torture/pr69613.c  2016-02-27 14:25:05.371834694 
+0100
@@ -1,6 +1,7 @@
 /* PR target/69613.  */
 /* { dg-do run { target int128 } } */
-/* { dg-additional-options "-mavx" { target { i?86-*-* x86_64-*-* } } } */
+/* { dg-options "-w -Wno-psabi" } */
+/* { dg-additional-options "-mavx" { target avx_runtime } } */
 
 typedef unsigned short u16;
 typedef unsigned short v32u16 __attribute__ ((vector_size (32)));

Jakub


Re: [patch, fortran] PR69110 ICE with NEWUNIT

2016-02-27 Thread Tom de Vries

On 25-02-16 01:54, Jerry DeLisle wrote:

This patch from Steve on c.l.f

Fixes the segfault from attempting a string compare where there is no string 
yet.

Regression tested on x86-64.  New test case.

OK for trunk.

Regards,

Jerry

2016-02-24  Jerry DeLisle  
Steven G. Kargl  

PR fortran/69110


I suppose you mean 69910?

Thanks,
- Tom



Re: [patch, fortran] PR69110 ICE with NEWUNIT

2016-02-27 Thread Jerry DeLisle
On 02/27/2016 01:12 PM, Tom de Vries wrote:
> On 25-02-16 01:54, Jerry DeLisle wrote:
>> This patch from Steve on c.l.f
>>
>> Fixes the segfault from attempting a string compare where there is no string 
>> yet.
>>
>> Regression tested on x86-64.  New test case.
>>
>> OK for trunk.
>>
>> Regards,
>>
>> Jerry
>>
>> 2016-02-24  Jerry DeLisle  
>> Steven G. Kargl  
>>
>> PR fortran/69110
> 
> I suppose you mean 69910?
> 
> Thanks,
> - Tom
> 
> 
Yes, sorry about that.

Will fix

Jerry


[wwwdocs] Update link for Openbench

2016-02-27 Thread Gerald Pfeifer
Update link for Openbench.

Applied.

Gerald

Index: benchmarks/index.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/benchmarks/index.html,v
retrieving revision 1.33
diff -u -r1.33 index.html
--- benchmarks/index.html   14 Nov 2015 21:42:23 -  1.33
+++ benchmarks/index.html   27 Feb 2016 22:43:04 -
@@ -93,7 +93,7 @@
 Openbench
 
 
-http://exactcode.de/site/open_source/openbench/";>Openbench
+http://exactcode.com/opensource/openbench/";>Openbench
 is a free benchmarking suite similar to SPEC.
 
 


Re: [PATCH] [RFA] [PR tree-optmization/69740] Schedule loop fixups when needed

2016-02-27 Thread H.J. Lu
On Thu, Feb 25, 2016 at 11:50 PM, Jeff Law  wrote:
> On 02/25/2016 03:00 AM, Richard Biener wrote:
>>
>>
>> So I fail to see how only successor edges are relevant.  Isn't the
>> important
>> case to catch whether we remove an edge marked EDGE_IRREDUCIBLE_LOOP?
>> Even if the BB persists we might have exposed a new loop here.
>>
>> Note that it is not safe to look at {BB,EDGE}_IRREDUCIBLE_LOOP if the loop
>> state does not have LOOPS_HAVE_MARKED_IRREDUCIBLE_REGIONS set
>> (the flags may be stale or missing).  So it might be that we can't rely on
>> non-loop passes modifying the CFG to handle this optimistically.
>>
>> Thus, how about (my main point) moving this to remove_edge instead, like
>
> Yea.  That works.  The !loops_state_satisfies_p check will almost certainly
> cause us to trigger loop cleanups more often, but I think it's the
> right/safe thing to do to catch cases where we haven't go the
> IRREDUCIBLE_LOOP flags set.
>
>
> Bootstrapped and regression tested on x86_64-linux-gnu.  OK for the trunk?
>
> Thanks,
> Jeff
>
>
> PR tree-optimization/69740
> * cfghooks.c (remove_edge): Request loop fixups if we delete
> an edge that might turn an irreducible loop into a natural
> loop.
>
> PR tree-optimization/69740
> * gcc.c-torture/compile/pr69740-1.c: New test.
> * gcc.c-torture/compile/pr69740-2.c: New test.
>

This caused:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69996

and may be other build failures in SPEC CPU 2006.


H.J.