Sorry for forgetting using plain-text mode. Resend it.
-- Forwarded message --
From: Cong Hou
Date: Mon, Oct 14, 2013 at 3:29 PM
Subject: Re: [PATCH] Reducing number of alias checks in vectorization.
To: Richard Biener , GCC Patches
Cc: Jakub Jelinek
I have made a new patch f
This patch from Chris Manghane changes the Go frontend to use the
backend interface for map and type descriptors. Bootstrapped and ran Go
testsuite on x86_64-unknown-linux-gnu. Committed to mainline.
Ian
2013-10-14 Chris Manghane
* go-gcc.cc (Gcc_backend::address_expression): New f
Any comment on this patch?
thanks,
Cong
On Thu, Oct 3, 2013 at 3:59 PM, Cong Hou wrote:
> During loop versioning in vectorization, the alias check guarantees
> that any load of a data reference with zero-step is a loop invariant,
> which can be hoisted outside of the loop. After hoisting the l
On Mon, 14 Oct 2013, Dodji Seketeli wrote:
> > This patch has passes the existing -Wconversion testcases. It modifies
> > Wconversion-real.c, Wconversion-real-integer.c and pr35635.c to be more
> > specific
>
> If the patch passes existing tests, I'd be inclined to leave them
> tests alone and a
On Sep 25, 2012, at 8:00 AM, Richard Guenther wrote:
> 2012-09-25 Richard Guenther
>
> PR lto/54625
> * lto-symtab.c (lto_symtab_merge_cgraph_nodes_1): Do not merge
> cgraph nodes for builtins.
>
> * gcc.dg/lto/pr54702_0.c: New testcase.
> * gcc.dg/lto/pr54702_1.
Ping...
thanks,
Cong
On Wed, Oct 2, 2013 at 11:18 AM, Cong Hou wrote:
> Ping.. Any comment on this patch?
>
>
> thanks,
> Cong
>
>
> On Sat, Sep 28, 2013 at 9:34 AM, Xinliang David Li wrote:
>> You can also add a test case of this form:
>>
>> int foo( int t, int n, int *dst)
>> {
>>int j
> [gcc]
> 2013-10-11 Michael Meissner
>
> PR target/58673
> * config/rs6000/rs6000.c (rs6000_legitimate_address_p): Only
> restrict TImode addresses to single indirect registers if both
> -mquad-memory and -mvsx-timode are used.
> (rs6000_output_move_128bi
On Mon, Oct 7, 2013 at 7:00 PM, Michael Meissner
wrote:
> On this patch, I add some infrastructure to say whether a given mode can go in
> a general purpose register, floating point register, or altivec register, and
> if it can, what kinds of addressing is legal for the mode. In addition, I
> h
I've pushed the following to the "dmalcolm/jit" branch:
http://gcc.gnu.org/git/?p=gcc.git;a=commit;h=6cc326e5ad7c269a295fb6108e34b5c885a96b12
This patch implements gcc_jit_location, so that client code can mark
the various constructs with an underlying code location. For example, a
JIT compiler f
Committed to dmalcolm/jit.
---
gcc/jit/ChangeLog.jit | 4
gcc/jit/libgccjit.map | 61 ++-
2 files changed, 35 insertions(+), 30 deletions(-)
diff --git a/gcc/jit/ChangeLog.jit b/gcc/jit/ChangeLog.jit
index 5c06a72..d998134 100644
--- a/gcc/ji
Committed to dmalcolm/jit.
---
gcc/testsuite/ChangeLog.jit | 5 +
gcc/testsuite/jit.dg/jit.exp | 8 ++--
2 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/gcc/testsuite/ChangeLog.jit b/gcc/testsuite/ChangeLog.jit
index 3d63d4b..6324e9e 100644
--- a/gcc/testsuite/ChangeLog.j
The reason for the failure was that UNLIMITED_POLY (from_expr) is no
longer true after one did a gfc_add_vptr_component (from_expr);
As vtab is only NULL for unlimited polymorphic [CLASS(*)], I use it now
instead.
Build and regtested on x86-64-gnu-linux.
Committed as Rev. 203586.
Tobias
2013-
Il 15/10/2013 00:28, Gerald Pfeifer ha scritto:
> - The problem is not actually the set of flags being used. On a
>different tester clang is the bootstrap compiler, and this is
>also the one invoked for `gmake install`. If anything, shouldn't
>the just built compiler be used _if_ an
101 - 113 of 113 matches
Mail list logo
