Within cp/parser.c, cp_lexer_peek_token and the rest of the
token-related functions are bloated by lexer-debugging code, code that
is completely dead unless calls to the functions
cp_lexer_[start|stop]_debugging are deliberately inserted somewhere in
the parser source code for temporary debugging
include/c_compatibility/stdlib.h imports wide character related symbols
into global namespace unconditionaly which causes libstdc++-v3 build
to fail when one or both of _GLIBCXX_USE_WCHAR_T and _GLIBCXX_HAVE_MBSTATE_T
are not defined.
Included patch changes it to import them into global
On 2016/1/25 7:06 PM, Jakub Jelinek wrote:
> The following ICEs without the patch and works with it, so I think it is
> better:
>
> 2016-01-25 Jakub Jelinek
>
> * omp-low.c (lower_omp_target) : Set
> DECL_VALUE_EXPR of new_var even for the non-array case. Look
>
Hi,
On Mon, 25 Jan 2016, Uros Bizjak wrote:
> This patch caused bootstrap failure on non-c++11 bootstrap compiler
> [1], e.g. CentOS 5.11.
>
> The problem is with std::swap, which was defined in header
> until c++11 [2].
>
> [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69464
> [2]
On 25/01/16 13:33, Claudiu Zissulescu wrote:
Please find attached two small patches which are fixing two issues within the
ARC backend:
1. The first one fixes predicates used by arcset* patterns.
2. The second one rejects constant-constant comparisons. This situation may
happen durring CSE
On Mon, Jan 25, 2016 at 11:16 AM, Ilya Enkovich wrote:
> Hi,
>
> This patch covers one more case when boolean operands get different
> vectypes and we don't detect it.
>
> Bootstrapped and regtested on x86_64-pc-linux-gnu. OK for trunk?
Ok.
Richard.
> Thanks,
> Ilya
>
On 22 January 2016 at 18:07, Richard Henderson wrote:
> The bare CONST_INT inside the CCmode IF_THEN_ELSE is causing combine to make
> incorrect simplifications. At this stage it feels safer to wrap the
> CONST_INT inside of an UNSPEC than make more generic changes to combine.
>
Hi!
On Tue, Jan 05, 2016 at 15:56:15 +0100, Tom de Vries wrote:
> >diff --git a/gcc/lto-cgraph.c b/gcc/lto-cgraph.c
> >index 62e5454..cdaee41 100644
> >--- a/gcc/lto-cgraph.c
> >+++ b/gcc/lto-cgraph.c
> >@@ -1911,6 +1911,11 @@ input_offload_tables (void)
> > tree fn_decl
> >
On 01/16/2016 11:00 AM, Jan Hubicka wrote:
> Can't it be represented via explicit REF_ADDR or something like that?
>
> Honza
Hi.
Sure, I've just done a patch that can do that. However, as we're currently in
stage4,
that change would probably require explicit permission of a release manager?
On Fri, Jan 22, 2016 at 7:55 PM, H.J. Lu wrote:
> Without the fix for PR 65656, g++ miscompiles __builtin_constant_p in
> wi::lrshift in wide-int.h. Add a check with PR 65656 testcase to verify
> that C++ __builtin_constant_p works properly.
>
> Tested on x86-64 with
On Sun, Jan 24, 2016 at 9:17 PM, Bill Schmidt
wrote:
> Hi Jan, thanks for the report! Patch below that should fix the problem.
> Bootstrapped and tested on powerpc64le-unknown-linux-gnu, no
> regressions. David, is this ok for trunk?
>
> Thanks,
> Bill
>
>
>
On 22 January 2016 at 18:06, Alan Lawrence wrote:
> On 20/01/16 21:10, Christophe Lyon wrote:
>>
>> On 19 January 2016 at 15:51, Alan Lawrence
>> wrote:
>>>
>>> On 19/01/16 11:15, Christophe Lyon wrote:
>>>
>> For neon_vdupn, I chose to
On Mon, Jan 25, 2016 at 10:06:50AM -0500, Nathan Sidwell wrote:
> On 01/04/16 10:39, Nathan Sidwell wrote:
> >There's currently no robust predicate to determine whether an oacc offload
> >function is for a kernels region (as opposed to a parallel region). The
> >test in
> >tree-ssa-loop.c uses
Please find attached two small patches which are fixing two issues within the
ARC backend:
1. The first one fixes predicates used by arcset* patterns.
2. The second one rejects constant-constant comparisons. This situation may
happen durring CSE step.
Ok to apply?
Claudiu
Claudiu Zissulescu
gcc/
2016-01-25 Claudiu Zissulescu
* config/arc/arc.md (cstoresi4): Force operand into register.
(arcset): Fix predicate.
(arcsetltu): Likewise.
(arcsetgeu): Likewise.
(arcsethi): Likewise.
(arcsetls): Likewise.
---
gcc/
2016-01-25 Claudiu Zissulescu
* config/arc/predicates.md (proper_comparison_operator): Reject
constant-constant comparison.
---
gcc/config/arc/predicates.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gcc/config/arc/predicates.md
Tested on x86_64-linux, applied.
Richard.
2016-01-25 Richard Biener
PR testsuite/69380
* g++.dg/tree-ssa/pr69336.C: Restrict to x86_64 and i?86.
Index: gcc/testsuite/g++.dg/tree-ssa/pr69336.C
> FWIW, there's probably a missed optimization here - these constant -
> constant comparisons could be folded down further.
They are. The issue is when the CSE runs, wants to validate a new instruction
with the propagated constant, which will lead to errors as it checks the
On 01/22/2016 05:30 PM, Patrick Palka wrote:
On Fri, 22 Jan 2016, Jason Merrill wrote:
On 01/22/2016 11:17 AM, Patrick Palka wrote:
On Thu, 21 Jan 2016, Patrick Palka wrote:
On Thu, 21 Jan 2016, Jason Merrill wrote:
On 01/19/2016 10:30 PM, Patrick Palka wrote:
*
On 01/04/16 10:39, Nathan Sidwell wrote:
There's currently no robust predicate to determine whether an oacc offload
function is for a kernels region (as opposed to a parallel region). The test in
tree-ssa-loop.c uses the heuristic of seeing if all the dimensions are defaulted
(which can
Hi,
On Fri, 22 Jan 2016, Jakub Jelinek wrote:
> > > This may have caused:
> > >
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69434
> >
> > Guess we need:
> >
> > 2016-01-22 Jakub Jelinek
> >
> > PR bootstrap/69434
> > * genrecog.c: Define INCLUDE_ALGORITHM
On Mon, 25 Jan 2016, Michael Matz wrote:
> Hi,
>
> On Mon, 25 Jan 2016, Uros Bizjak wrote:
>
> > This patch caused bootstrap failure on non-c++11 bootstrap compiler
> > [1], e.g. CentOS 5.11.
> >
> > The problem is with std::swap, which was defined in header
> > until c++11 [2].
> >
> > [1]
Thanks, committed as r232793.
Bill
On Mon, 2016-01-25 at 08:54 -0500, David Edelsohn wrote:
> On Sun, Jan 24, 2016 at 9:17 PM, Bill Schmidt
> wrote:
>
> > Hi Jan, thanks for the report! Patch below that should fix the problem.
> > Bootstrapped and tested on
On Mon, 25 Jan 2016, Tom de Vries wrote:
> On 27/11/14 15:13, Richard Biener wrote:
> >
> > Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
> >
> > Richard.
> >
> > 2014-11-27 Richard Biener
> >
> > PR tree-optimization/64088
> > *
On Mon, Jan 25, 2016 at 04:21:50PM +0100, Martin Liška wrote:
> On 01/16/2016 11:00 AM, Jan Hubicka wrote:
> > Can't it be represented via explicit REF_ADDR or something like that?
> >
> > Honza
>
> Hi.
>
> Sure, I've just done a patch that can do that. However, as we're currently in
> stage4,
On 27/11/14 15:13, Richard Biener wrote:
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2014-11-27 Richard Biener
PR tree-optimization/64088
* tree-ssa-tail-merge.c (update_debug_stmt): After resetting
the stmt
ping
On Tue, Jan 19, 2016 at 9:28 AM, Ryan Burn wrote:
> Does this look ok?
>
>> On Jan 15, 2016, at 5:41 PM, Ryan Burn wrote:
>>
>> This patch changes the function cilk_gimplify_call_params_in_spawned_fn to
>> use gimplify_arg instead of
On 01/22/2016 05:07 PM, Marek Polacek wrote:
On Fri, Jan 22, 2016 at 03:38:26PM -0500, Jason Merrill wrote:
If we have a NOP_EXPR to the same type, we should strip it here.
This helps for the unreduced testcases in the PR, but not for the reduced one,
because for the reduced one, the types
Hi!
The soft-fp multilib of powerpc libgcc doesn't build because of a typo
in the conditional - the guarded code uses inline asm that assumes hard
float.
Ok for trunk?
2016-01-25 Jakub Jelinek
PR target/69444
* config/rs6000/sfp-machine.h: Fix a typo in
This is the first of a few patches to address 69196 (code size
regression with jump threading) and 68398 (coremark regression due to
FSM changes).
While these are caused by distinct issues, they hit the same hunk of
code. I could address them independently, but I believe in the end
it'll
On Mon, Jan 25, 2016 at 4:40 AM, Richard Biener
wrote:
> On Fri, Jan 22, 2016 at 7:55 PM, H.J. Lu wrote:
>> Without the fix for PR 65656, g++ miscompiles __builtin_constant_p in
>> wi::lrshift in wide-int.h. Add a check with PR 65656 testcase to
On 22 January 2016 at 12:56, Richard Biener wrote:
> On Fri, Jan 22, 2016 at 12:41 PM, Christian Bruel
> wrote:
>>
>>
>> On 01/19/2016 04:18 PM, Richard Biener wrote:
>>>
>>> maybe just if (currently_expanding_to_rtl)?
>>>
>>> But yes, this
Here's an updated version of the patch.
On Wed, 2016-01-13 at 18:32 +0100, Bernd Schmidt wrote:
> On 01/13/2016 01:57 AM, David Malcolm wrote:
> > There are five places in trunk that can call diagnostic_show_locus.
>
> I'd kind of like to see before/after example output for all of these, to
>
Bernd Edlinger writes:
> Matthew Fortune writes:
> > Has the patch been tested beyond just building GCC? I can do a
> > test run for you if you don't have things set up to do one yourself.
>
> I built a cross-gcc with all languages and a
On Mon, Jan 25, 2016 at 10:08:34AM -0500, Jason Merrill wrote:
> On 01/22/2016 05:07 PM, Marek Polacek wrote:
> >On Fri, Jan 22, 2016 at 03:38:26PM -0500, Jason Merrill wrote:
> >>If we have a NOP_EXPR to the same type, we should strip it here.
> >
> >This helps for the unreduced testcases in the
Andreas Schwab wrote:
> FAIL: gcc.target/aarch64/ccmp_1.c scan-assembler-times \tcmp\tw[0-9]+, 0 4
> FAIL: gcc.target/aarch64/ccmp_1.c scan-assembler adds\t
> FAIL: gcc.target/aarch64/ccmp_1.c scan-assembler-times fccmpe\t.*0\\.0 1
Yes I noticed those too, and here is the
Hi!
Here is an attempt to handle -f{,no-}sanitize= options in LTO wrapper.
In addition to that I've noticed ICEs e.g. if some OpenMP code is compiled
with -c -flto -fopenmp, but final link is -fno-openmp, similarly for
openacc, -fcilkplus is similar but used to be handled even less.
The intended
On 22/01/16 14:51, Christian Bruel wrote:
Hi Kyrill,
On 01/22/2016 03:17 PM, Kyrill Tkachov wrote:
Hi Christian,
On 22/01/16 14:07, Christian Bruel wrote:
Hi Kyrill,
On 01/21/2016 01:22 PM, Kyrill Tkachov wrote:
Hi Christian,
On 21/01/16 10:36, Christian Bruel wrote:
The current
On Mon, 2016-01-25 at 18:51 +0100, Paul Richard Thomas wrote:
> On 25 January 2016 at 18:33, Peter Bergner wrote:
>> I'll leave it to you or someone else to fix the -m32 bug, since
>> I'm not seeing it on my system.
>
> Neither am I :-(
I have a powerpc64-linux (ie, BE)
Ping.
On 27/10/15 17:03, Andre Vieira wrote:
Ping.
BR,
Andre
On 13/10/15 18:01, Andre Vieira wrote:
This patch ports the aeabi_idiv routine from Linaro Cortex-Strings
(https://git.linaro.org/toolchain/cortex-strings.git), which was
contributed by ARM under Free BSD license.
The new
On 01/25/2016 01:32 AM, Kyrill Tkachov wrote:
> +case CONST_WIDE_INT:
> + *cost = 0;
> + for (unsigned int n = CONST_WIDE_INT_NUNITS(x), i = 0; i < n; ++i)
> +{
> + unsigned HOST_WIDE_INT e = CONST_WIDE_INT_ELT(x, i);
> + if (e != 0)
> +*cost += COSTS_N_INSNS
After having just spent a few days looking through dumps of
builtin-overflow-*.c for regressions while testing the patch for the TImode
arithmetic PR, I thought I'd go ahead and post a patch to make use of the
overflow bit on aarch64.
Consider this queued for stage1.
r~
*
Ping: I'm looking a review/approval of the almost trivial patch
below:
https://gcc.gnu.org/ml/gcc-patches/2016-01/msg01206.html
On 01/16/2016 05:42 PM, Martin Sebor wrote:
While adding an ABI warning in the patch for bug 69277 I noticed
that the ABI version printed by GCC 6.0 in some -Wabi
On 01/25/2016 05:28 AM, Christophe Lyon wrote:
> After this, I'm seeing this test now FAILs:
> gcc.target/aarch64/ccmp_1.c scan-assembler adds\t
That test case is badly written. In addition to that one, several of the other
failures that I see within that file are simply equally optimal
In C++11 mode defines std::shuffle which uses
std::uniform_int_distribution. It doesn't need the rest of ,
which is huge, especially on x86 with SSE3 support, where pmmintrin.h
is pulled in.
This moves the definition of std::uniform_int_distribution to a new
header, and makes include that
When the test case derived_constructor_comps_6.f90 was backported to
the FSF 5 branch, a '}' on the dg-additional-options was dropped
causing the test case to fail. I have added it back and committed
it as obvious.
Peter
PR fortran/61831
*
On Mon, Jan 25, 2016 at 3:39 AM, Bernd Schmidt wrote:
> On 01/23/2016 12:52 AM, Ian Lance Taylor wrote:
>
>> 2016-01-22 Ian Lance Taylor
>>
>> * common.opt (fkeep-gc-roots-live): New option.
>> * tree-ssa-loop-ivopts.c (add_candidate_1): If
>>
From: Trevor Saunders
Hi,
$subject. To avoid regressions I kept the checks when generating rtl, but I
believe its impossible for those to trigger now and we can remove the checks.
bootstrapped + regtested on x86_64-linux-gnu, ok?
Trev
gcc/c/ChangeLog:
2016-01-25
On 01/25/2016 04:36 PM, tbsaunde+...@tbsaunde.org wrote:
$subject. To avoid regressions I kept the checks when generating rtl, but I
believe its impossible for those to trigger now and we can remove the checks.
bootstrapped + regtested on x86_64-linux-gnu, ok?
Is this still an issue? I
On Mon, Jan 25, 2016 at 04:42:58PM +0100, Bernd Schmidt wrote:
> On 01/25/2016 04:36 PM, tbsaunde+...@tbsaunde.org wrote:
> >$subject. To avoid regressions I kept the checks when generating rtl, but I
> >believe its impossible for those to trigger now and we can remove the checks.
> >
>
On 01/21/2016 04:32 PM, Martin Sebor wrote:
On 01/21/2016 04:19 PM, Jason Merrill wrote:
Can we reconsider the representation of flexible arrays? Following the
example of the C front-end is causing a lot of trouble, and using a null
TYPE_DOMAIN seems more intuitive.
I remember running into
Dear Peter,
Many thanks! I have been away, got back last night and had intended to
deal with it tonight. You should note that Dominique has flagged up
that it fails with -m32.
Tshuess
Paul
On 25 January 2016 at 18:09, Peter Bergner wrote:
> When the test case
On 01/23/2016 06:09 AM, Ajit Kumar Agarwal wrote:
This patch improves the updated memory cost in coloring pass of integrated
register
allocator. Only enter_freq of the loop is considered in updated memory cost in
the
coloring pass. Consideration of only enter_freq is based on the concept that
On Mon, 2016-01-25 at 18:17 +0100, Paul Richard Thomas wrote:
> Many thanks! I have been away, got back last night and had intended
> to deal with it tonight.
No problem.
> You should note that Dominique has flagged up that it fails with
> -m32.
I was building on powerpc64le-linux (which
Neither am I :-(
Paul
On 25 January 2016 at 18:33, Peter Bergner wrote:
> On Mon, 2016-01-25 at 18:17 +0100, Paul Richard Thomas wrote:
>> Many thanks! I have been away, got back last night and had intended
>> to deal with it tonight.
>
> No problem.
>
>
>> You should note
On Jan 22, 2016, at 2:16 AM, Jakub Jelinek wrote:
> On Thu, Jan 21, 2016 at 04:24:46PM +0100, Bernd Schmidt wrote:
>> Thomas, I've mentioned this issue before - there is sometimes just too much
>> irrelevant stuff to wade through in your patch submissions, and it
>> discourages
Richard Henderson wrote:
> On 01/25/2016 05:28 AM, Christophe Lyon wrote:
> > After this, I'm seeing this test now FAILs:
> > gcc.target/aarch64/ccmp_1.c scan-assembler adds\t
>
> That test case is badly written. In addition to that one, several of the
> other
> failures that I see within that
On Jan 25, 2016, at 4:15 AM, James Greenhalgh wrote:
P.S.: I haven't signed the copyright assignment to the FSF. The change
is really small but I can do the paperwork if required.
>
> I can't commit it on your behalf until we've heard back regarding whether
>
Hi!
The early-debug changes moved warnings about unused functions into cgraph.
The problem is that if we have just unused declarations, they aren't
sometimes even registered with cgraph and therefore we no longer warn.
Here is an attempt to register those with cgraph anyway to get the warning,
On 01/25/2016 12:09 PM, Wilco Dijkstra wrote:
> BTW is there a regular expression that correctly implements (0|xzr)?
(0|wzr) works fine for me; I've got exactly that fix in one of my trees.
r~
Dear All,
The initial report concerns initialization assignments that should be
excluded from the check for assignment of scalars to unallocated
arrays. This part is so trivial that it does not require a test. On
the other hand, the block that implemented the check was plain and
simple wrong and
Hi Paul,
seems we were pretty well-synchronized in posting this (in the PR it
sounded as if you wanted me to submit it ...)
In any case, the patch is ok for my taste.
Thanks!
Cheers,
Janus
2016-01-25 22:02 GMT+01:00 Paul Richard Thomas :
> Dear All,
>
> The
On Mon, Jan 25, 2016 at 3:34 PM, Jakub Jelinek wrote:
> Hi!
>
> The soft-fp multilib of powerpc libgcc doesn't build because of a typo
> in the conditional - the guarded code uses inline asm that assumes hard
> float.
>
> Ok for trunk?
>
> 2016-01-25 Jakub Jelinek
This issue also remains in 4.9 and 5.0 branches. Is this OK to backport
to the release branches.
Thanks,
Kugan
On 02/12/15 10:00, Kugan wrote:
>
>>>
>>> gcc/ChangeLog:
>>>
>>> 2015-11-18 Kugan Vivekanandarajah
>>>
>>> PR target/68390
>>> * config/arm/arm.c
---
gcc/testsuite/gcc.dg/graphite/pr69292.c | 19 +++
1 file changed, 19 insertions(+)
create mode 100644 gcc/testsuite/gcc.dg/graphite/pr69292.c
diff --git a/gcc/testsuite/gcc.dg/graphite/pr69292.c
b/gcc/testsuite/gcc.dg/graphite/pr69292.c
new file mode 100644
index
The attached patch adjusts the documentation of attribute aligned
and attribute pack so as to prevent misreading the text of the
former attribute as if it had read:
Specifying attribute aligned for struct and union types is
equivalent to specifying the packed attribute on each of
the
> On Mon, Jan 25, 2016 at 04:21:50PM +0100, Martin Liška wrote:
> > On 01/16/2016 11:00 AM, Jan Hubicka wrote:
> > > Can't it be represented via explicit REF_ADDR or something like that?
> > >
> > > Honza
> >
> > Hi.
> >
> > Sure, I've just done a patch that can do that. However, as we're
The patch disables all fuse-*.c tests when configuring gcc with isl 0.14 or
earlier.
ChangeLog:
* Makefile.in: Regenerate.
* Makefile.tpl: Export ISLVER.
* configure: Regenerate.
* config/isl.m4: Detect isl-0.15.
gcc/
* Makefile.in: Set ISLVER in
Keep unchanged the implementation for isl-0.14.
* graphite-poly.c (apply_poly_transforms): Simplify.
(print_isl_set): Use more readable format: ISL_YAML_STYLE_BLOCK.
(print_isl_map): Same.
(print_isl_union_map): Same.
(print_isl_schedule): New.
gccjit currently fails to build, needing an additional header. Ok to install on
the trunk?
Matthias
* jit-playback.c: Include .
--- a/gcc/jit/jit-playback.c
+++ b/gcc/jit/jit-playback.c
@@ -43,6 +43,8 @@ along with GCC; see the file COPYING3.
#include "jit-builtins.h"
#include
Hi David,
On Sun, Jan 24, 2016 at 02:23:53PM -0800, David Wohlferd wrote:
> - Warn that this could change in future versions of gcc. To avoid
> impacts from this change, use extended asm.
> - Implement and document -Wonly-top-basic-asm (disabled by default) as a
> way to locate affected
On Sat, 2016-01-23 at 19:08 +0100, Iain Buclaw wrote:
> Hi,
>
> I noticed when building from 2016-01-17 snapshot that the JIT frontend
> failed to build.
>
> ---
> jit-playback.c:2075:36: error: ‘PTHREAD_MUTEX_INITIALIZER’ was not
> declared in this scope
> jit-playback.c: In member function
Stack alignment adjustment for __tls_get_addr should be done in
ix86_update_stack_boundary, not ix86_compute_frame_layout. Also
there is no need to over-align stack for __tls_get_addr and function
with __tls_get_addr call isn't a leaf function.
Tested on x86-64 with -m32 on testsuite. OK for
On 2016/1/22 12:32 AM, Jakub Jelinek wrote:
> On Thu, Jan 21, 2016 at 10:22:19PM +0800, Chung-Lin Tang wrote:
>> On 2016/1/20 09:17 PM, Bernd Schmidt wrote:
>>> On 01/05/2016 02:15 PM, Chung-Lin Tang wrote:
* omp-low.c (scan_sharing_clauses): Call add_local_decl() for
Hi!
Committed to gomp-4_0-branch in r232784:
commit 9cfa5d5eb5fd3b186124883a76232189b359b3de
Merge: 312e74d 56778b6
Author: tschwinge
Date: Mon Jan 25 07:35:18 2016 +
svn merge -r 232189:232548 svn+ssh://gcc.gnu.org/svn/gcc/trunk
The following fixes an issue with LTO and debug info of OMP vars.
LTO bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2016-01-25 Richard Biener
PR lto/69393
* dwarf2out.c (is_naming_typedef_decl): Not when DECL_NAMELESS.
*
Hi Richard,
On 24/01/16 10:54, Richard Henderson wrote:
This looks to be an incomplete transition of the aarch64 backend to
CONST_WIDE_INT. I haven't checked to see if it's a regression from gcc5, but I
suspect not, since there should have been similar checks for CONST_DOUBLE.
FWIW, I
On Mon, Jan 25, 2016 at 05:52:56PM +0900, Chung-Lin Tang wrote:
> I've attached a small testcase that triggers the ICE under -fopenacc. This
> stll
> happens under current trunk.
Then I think I'd prefer (untested so far):
2016-01-25 Jakub Jelinek
* omp-low.c
Hi,
This is an obvious patch fixing a verbosity for a part of error messages.
Bootstrapped on x86_64-pc-linux-gnu. Applied to trunk and gcc-5-branch.
Thanks,
Ilya
--
libmpx/
2016-01-20 Ilya Enkovich
* mpxrt/mpxrt.c (handler): Fix verbosity for
On Mon, Jan 25, 2016 at 11:02:05AM +0100, Jakub Jelinek wrote:
> On Mon, Jan 25, 2016 at 10:58:17AM +0100, Jakub Jelinek wrote:
> > --- gcc/testsuite/c-c++-common/goacc/use_device-1.c.jj 2016-01-25
> > 10:56:33.472310437 +0100
> > +++ gcc/testsuite/c-c++-common/goacc/use_device-1.c
The following makes SCCVN properly save/restore SSA_NAME_ANTI_RANGE_P.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2016-01-25 Richard Biener
PR tree-optimization/69376
* tree-ssa-sccvn.h (struct vn_ssa_aux): Add
On Mon, Jan 25, 2016 at 10:58:17AM +0100, Jakub Jelinek wrote:
> --- gcc/testsuite/c-c++-common/goacc/use_device-1.c.jj2016-01-25
> 10:56:33.472310437 +0100
> +++ gcc/testsuite/c-c++-common/goacc/use_device-1.c 2016-01-25
> 10:56:43.128176481 +0100
> @@ -0,0 +1,15 @@
> +/* { dg-do
On 14/01/16 10:43, Richard Biener wrote:
On Wed, Jan 13, 2016 at 9:04 PM, Tom de Vries wrote:
Hi,
At r231739, there was an ICE when checking code generated by
oacc_xform_loop, in case the source contained an error.
Due to seen_error (), gimplification during
On Mon, Jan 11, 2016 at 12:04:43PM +, James Greenhalgh wrote:
>
> Hi,
>
> I've seen a couple of large performance issues caused by expanding
> the high-precision reciprocal square root for Cortex-A57, so I'd like
> to turn it off by default.
>
> This is good for art (~2%) from Spec2000, bad
Hi,
This patch covers one more case when boolean operands get different
vectypes and we don't detect it.
Bootstrapped and regtested on x86_64-pc-linux-gnu. OK for trunk?
Thanks,
Ilya
--
gcc/
2016-01-25 Ilya Enkovich
PR target/69421
*
Committed r232788
Thanks,
Claudiu
> -Original Message-
> From: Joern Wolfgang Rennecke [mailto:g...@amylaar.uk]
> Sent: Sunday, January 24, 2016 3:26 PM
> To: Claudiu Zissulescu; gcc-patches@gcc.gnu.org
> Cc: Francois Bedard; jeremy.benn...@embecosm.com
> Subject: Re: [PATCH] [ARC] Add
On Mon, Jan 11, 2016 at 11:53:39AM +, James Greenhalgh wrote:
>
> Hi,
>
> I'd like to switch the logic around in aarch64.c such that
> -mlow-precision-recip-sqrt causes us to always emit the low-precision
> software expansion for reciprocal square root. I have two reasons to do
> this; first
On 01/23/2016 12:52 AM, Ian Lance Taylor wrote:
2016-01-22 Ian Lance Taylor
* common.opt (fkeep-gc-roots-live): New option.
* tree-ssa-loop-ivopts.c (add_candidate_1): If
-fkeep-gc-roots-live, skip pointers.
(add_iv_candidate_for_biv): Handle add_candidate_1 returning
NULL.
On Thu, Jan 21, 2016 at 12:32:07PM +, James Greenhalgh wrote:
> On Wed, Jan 13, 2016 at 05:44:30PM +, Bilyan Borisov wrote:
> > This patch implements all the vcvtR_s64_f64 and vcvtR_u64_f64 vector
> > intrinsics, where R is ['',a,m,n,p]. Since these intrinsics are
> > identical in
Tested on x86_64-suse-linux, applied on the mainline as obvious.
2016-01-25 Eric Botcazou
* doc/extend.texi (scalar_storage_order type attribute): Fix typo and
improve wording for mixed storage order support.
--
Eric BotcazouIndex: doc/extend.texi
On Wed, Jan 20, 2016 at 09:27:41PM +0100, Roger Ferrer Ibáñez wrote:
> Hi James,
>
> > This patch looks technically correct to me, though there is a small
> > style issue to correct (in-line below), and your ChangeLogs don't fit
> > our usual style.
>
> thank you very much for the useful
Hello!
> * system.h (string, algorithm): Include only conditionally.
> (new): Include always under C++.
> * bb-reorder.c (toplevel): Define USES_ALGORITHM.
> * final.c (toplevel): Ditto.
> * ipa-chkp.c (toplevel): Define USES_STRING.
> * genconditions.c (write_header): Make gencondmd.c define
>
On 01/24/2016 11:23 PM, David Wohlferd wrote:
+Wonly-top-basic-asm
+C ObjC ObjC++ C++ Var(warn_only_top_basic_asm) Warning
+Warn on unsafe uses of basic asm.
Maybe just -Wbasic-asm?
+/* Warn on basic asm used inside of functions,
+ EXCEPT when in naked functions. Also allow
It turns out the 's' output modifier is used in some glibc math code,
and is in an installed header even. So let's put it back, it is much
less of a burden supporting it a bit longer than to deal with the fallout.
(It is also being fixed for glibc.)
Tested on powerpc64-linux-gcc; is this okay
94 matches
Mail list logo