fragile test case ivopt_infer_2.c

2013-06-19 Thread Bin.Cheng
Hi, For test case gcc.dg/tree-ssa/ivopt_inter_2.c #ifndef TYPE #define TYPE char* #endif extern char a[]; /* Can not infer loop iteration from array -- exit test can not be replaced. */ void foo (unsigned int i_width, TYPE dst) { unsigned long long i = 0; unsigned long long j = 0; for ( ;

Re: fragile test case ivopt_infer_2.c

2013-06-19 Thread Richard Biener
On Wed, Jun 19, 2013 at 10:04 AM, Bin.Cheng wrote: > Hi, > For test case gcc.dg/tree-ssa/ivopt_inter_2.c > > #ifndef TYPE > #define TYPE char* > #endif > > extern char a[]; > > /* Can not infer loop iteration from array -- exit test can not be replaced. > */ > void foo (unsigned int i_width, TYP

GCC 4.6 missing plugin headers

2013-06-19 Thread Alex Leach
Hi, I built and installed GCC 4.6.4 last night - on amd64 Linux 3.9.6 - and the installation was missing c-family/c-common.h from its plugin directory. This header is installed by 4.7 and 4.8 branches, and is included by other core plugin headers on 4.6, e.g. cp/cp-tree.h, which my plugin

Re: GCC 4.6 missing plugin headers

2013-06-19 Thread Jakub Jelinek
On Wed, Jun 19, 2013 at 10:47:09AM +0100, Alex Leach wrote: > Are there any further releases planned for the 4.6 branch? Would a > patch be accepted for this? I've got the 4.6 branch checked out in > git, but don't know exactly where an edit would be needed.. Are > there any reasons why this header

Re: fragile test case ivopt_infer_2.c

2013-06-19 Thread Bin.Cheng
On Wed, Jun 19, 2013 at 4:43 PM, Richard Biener wrote: > On Wed, Jun 19, 2013 at 10:04 AM, Bin.Cheng wrote: >> Hi, >> For test case gcc.dg/tree-ssa/ivopt_inter_2.c >> >> #ifndef TYPE >> #define TYPE char* >> #endif >> >> extern char a[]; >> >> /* Can not infer loop iteration from array -- exit te

Re: fragile test case ivopt_infer_2.c

2013-06-19 Thread Richard Biener
On Wed, Jun 19, 2013 at 12:35 PM, Bin.Cheng wrote: > On Wed, Jun 19, 2013 at 4:43 PM, Richard Biener > wrote: >> On Wed, Jun 19, 2013 at 10:04 AM, Bin.Cheng wrote: >>> Hi, >>> For test case gcc.dg/tree-ssa/ivopt_inter_2.c >>> >>> #ifndef TYPE >>> #define TYPE char* >>> #endif >>> >>> extern char

Re: fragile test case ivopt_infer_2.c

2013-06-19 Thread Bin.Cheng
On Wed, Jun 19, 2013 at 8:33 PM, Richard Biener wrote: > On Wed, Jun 19, 2013 at 12:35 PM, Bin.Cheng wrote: >> On Wed, Jun 19, 2013 at 4:43 PM, Richard Biener >> wrote: >>> On Wed, Jun 19, 2013 at 10:04 AM, Bin.Cheng wrote: Hi, For test case gcc.dg/tree-ssa/ivopt_inter_2.c #

[patch] libitm: Fix handling of reentrancy in the HTM fastpath

2013-06-19 Thread Torvald Riegel
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57643 The HTM fastpath didn't handle a situation in which a relaxed transaction executed unsafe code that in turn starts a transaction; it simply tried to wait for the "other" transaction, not checking whether the current thread started the other transac

Re: Libitm issues porting to POWER8 HTM

2013-06-19 Thread Peter Bergner
On Tue, 2013-06-18 at 21:48 +0200, Andi Kleen wrote: > > Given Torvald's comment, can you verify whether your hw txn succeeds > > (all the way to commit) or whether it is failing and somehow skips > > the fall through code that is hanging for us (Power and S390)? > > All the 3 transactions in reen

legitimate_address_p

2013-06-19 Thread Hendrik Greving
If the 'address' in question is (mem:m), then this is usually false is that right? Compiler always asks for the address excluding (mem:m), is that true (it would mean some kind of pointer to pointer)? Is this also true if reload check inline asm statements with memory constraints? Thanks, Hendrik

Re: legitimate_address_p

2013-06-19 Thread Hendrik Greving
I think the answer is yes, please disregard. On Wed, Jun 19, 2013 at 9:05 AM, Hendrik Greving wrote: > If the 'address' in question is (mem:m), then this is usually false is > that right? Compiler always asks for the address excluding (mem:m), is > that true (it would mean some kind of pointer t

Re: Libitm issues porting to POWER8 HTM

2013-06-19 Thread Andi Kleen
On Wed, Jun 19, 2013 at 11:04:25AM -0500, Peter Bergner wrote: > On Tue, 2013-06-18 at 21:48 +0200, Andi Kleen wrote: > > > Given Torvald's comment, can you verify whether your hw txn succeeds > > > (all the way to commit) or whether it is failing and somehow skips > > > the fall through code that

Re: Compiling GCC under Cygwin

2013-06-19 Thread Angelo Graziosi
Arjen Markus wrote: I am trying to compile GCC 4.8.1 under Cygwin. ../.././gcc/ada/gcc-interface/Make-lang.in:677: *** target pattern contains no `%'. Stop. make[3]: Leaving directory `/cygdrive/d/gcc-src/gcc-4.8.1/host-i686-pc-cygwin/gcc' Makefile:4160: recipe for target `all-stage1-gcc' failed

Re: Compiling GCC under Cygwin

2013-06-19 Thread Arjen Markus
Hi Angelo, true, it is not Fortran-specific. I used this mailing-list because I am familiar with it and because the purpose of this attempt was to see if I can in some way contribute other things than bug reports ;). The error you refer to is actually an error in the C source, whereas the build e

Re: Compiling GCC under Cygwin

2013-06-19 Thread Angelo Graziosi
Ciao Arjen, Il 19/06/2013 21.01, Arjen Markus ha scritto: As for the build experiment itself: - I downloaded the 4.8.1 source - I configured the Makefiles with this command: ./configure --prefix=d:/gcc-src/gcc Hmm... Cygwin doesn't like the path in the DOS style, "d:/...". At least it shou