On Sun, Dec 14, 2014 at 3:08 PM, H.J. Lu hjl.to...@gmail.com wrote:
The enclosed testcase fails on x86 when compiled with -Os since we pass
a byte parameter with a byte load in caller and read it as an int in
callee. The reason it only shows up with -Os is x86 backend encodes
a byte load
On Fri, Dec 12, 2014 at 10:33 PM, Jakub Jelinek ja...@redhat.com wrote:
Hi!
This patch ensures that if successor of entry bb has multiple predecessors,
we emit the __tsan_func_entry call on the edge from entry bb, so it can't
be called inside a loop in the same function.
On Mon, 15 Dec 2014, Jan Hubicka wrote:
Hi, actually this patch break fortran, I get streaming error in: lto1:
internal compiler error: in streamer_get_pickled_tree apparently picking
error_mark_node for variable constructor results in reading
integer_type...
?
Probably the default nodes
-Original Message-
From: Richard Henderson [mailto:r...@redhat.com]
Sent: Saturday, December 13, 2014 3:26 AM
To: Zhenqiang Chen
Cc: Marcus Shawcroft; gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, AARCH64] Fix ICE in CCMP (PR64015)
- tree lhs = gimple_assign_lhs (g);
Hi,
On 12 Dec 09:17, Jakub Jelinek wrote:
On Fri, Dec 12, 2014 at 09:14:28AM +0100, Thomas Schwinge wrote:
On Tue, 30 Sep 2014 13:16:37 +0200, I wrote:
On Fri, 26 Sep 2014 16:36:21 +0400, Ilya Verbin iver...@gmail.com wrote:
--- a/configure.ac
+++ b/configure.ac
@@ -286,6 +286,24
Eric Botcazou ebotca...@adacore.com writes:
FWIW I agree this is the right approach, although I can't approve it.
The assert above is guarding code that deals with a very general case,
including some unusual combinations, so I don't think it would be a
good idea to try to remove it entirely.
Thanks for the comments. Patch is updated.
diff --git a/gcc/combine.c b/gcc/combine.c
index 1808f97..2e865d7 100644
--- a/gcc/combine.c
+++ b/gcc/combine.c
@@ -1603,6 +1603,28 @@ setup_incoming_promotions (rtx_insn *first)
}
}
+/* Update RSP from INSN's REG_EQUAL note and SRC.
This patch should be applied to GCC mainline. I do not have write
access, so in case this gets approved, please commit it for me.
gcc/ChangeLog
2014-12-15 Sebastian Huber sebastian.hu...@embedded-brains.de
* config/arm/t-rtems: Use MULTILIB_REQUIRED instead of
Now that we only have the EABI configuration for RTEMS rename the files
to match the pattern used for the other RTEMS targets.
This patch should be applied to GCC mainline. I do not have write
access, so in case this gets approved, please commit it for me.
gcc/ChangeLog
2014-12-15 Sebastian
On Fri, Dec 12, 2014 at 10:14:21AM -0800, Richard Henderson wrote:
On 12/12/2014 04:06 AM, Dominik Vogt wrote:
I'm not sure I've posted the missing patch anywhere yet, so it's
attached to this message. At the moment it enables
FFI_TYPE_COMPLEX only for s390[x], but eventually this should
-Original Message-
From: Christophe Lyon [mailto:christophe.l...@linaro.org]
Sent: 11 December 2014 13:47
To: David Sherwood
Cc: gcc-patches@gcc.gnu.org; Marcus Shawcroft; Alan Hayward; Tejas Belagod;
Richard Sandiford
Subject: Re: New patch: [AArch64] [BE] [1/2] Make large
Do you have a reason for using fp-bit instead of soft-fp?
Apart from the obvious historical reason, probably not, but recently added
ports (Blackfin, Epiphany) also use it so I'm not sure we want to change it.
libgcc files are generally GPL+exception, not LGPL without exception with
a very
Hi!
As mentioned in the PR, some tests fail with -fpic.
The problem is that they are expecting a 32-bit GPR must start with
%e, but %r8d or %r15d are 32-bit GPRs too.
The other problem is that PIC code has some loads/stores different from
non-pic code, so the counts looking e.g. for loads with (
2014-12-15 7:34 GMT+01:00 Tobias Burnus bur...@net-b.de:
Can you change non-pure to impure? That would better match the Fortran
naming, where impure is the default unless pure or elemental is used.
(It was added to permit impure elemental procedures.)
Yes, sure. I have committed this change as
Hi!
The thread_local10.C fails, because if plugin.exp is sourced before tls.exp
on the 4.8 branch, DEFAULT_CXXFLAGS includes -ansi and the thread_local10.C
test, which is C++11, but has no dg-options, fails with:
/usr/src/gcc-4.8/gcc/testsuite/g++.dg/tls/thread_local10.C:11:10: error:
On Wed, Dec 10, 2014 at 9:08 PM, Jakub Jelinek ja...@redhat.com wrote:
As mentioned in the PR, some tests fail with -fpic.
The problem is that they are expecting a 32-bit GPR must start with
%e, but %r8d or %r15d are 32-bit GPRs too.
The other problem is that PIC code has some loads/stores
On Fri, Dec 12, 2014 at 1:21 PM, Zamyatin, Igor igor.zamya...@intel.com wrote:
When adding checks for PIC register in address cost calculation
(http://gcc.gnu.org/ml/gcc-cvs/2014-10/msg00411.html) it was meant to affect
only RTL passes.
Since !pic_offset_table_rtx is not enough for it (I
... committed as obvious the below.
Paolo.
/
2014-12-15 Paolo Carlini paolo.carl...@oracle.com
* g++.dg/cpp1y/pr63996.C: Fix.
Index: g++.dg/cpp1y/pr63996.C
===
--- g++.dg/cpp1y/pr63996.C
Hi!
This testcase fails on the 4.9 branch (where C89 is the default) on 32-bit
targets, because of
warning: this decimal constant is unsigned only in ISO C90
warning. On the trunk it doesn't warn because we default to C11. In any
case, the testcase also fails the same way before the r218205 fix
On 14/12/14 15:23 -0800, Tim Shen wrote:
Bootstraped and tested :)
I'm not sure if it's safe to directly backport it to 4.9, since one
inline function (_M_normalize_result) is added; but at least we can
manually inline them by copy paste.
It's OK for trunk and 4.9, without changes.
Code
If combine is given a parallel I2, it splits it into separate I1 and
I2 insns in some cases (one case since the beginning of time; more
cases since my r218248). It gives the new I1 the same UID as the I2
already has; there is a comment that this works fine because the I1
never is added to the
On 11/12/14 19:22 +0100, Kai-Uwe Eckhardt wrote:
--- libstdc++-v3/config/os/bsd/netbsd/ctype_base.h.orig 2014-12-10
22:18:50.0 +0100
+++ libstdc++-v3/config/os/bsd/netbsd/ctype_base.h 2014-12-10
22:20:31.0 +0100
@@ -43,9 +43,22 @@
// NB: Offsets into
If an addic. is split to addi+cmp (because RA didn't give it CR0), it will
do the wrong thing if the input reg is GPR0 (addi X,0,N is li X,N).
So don't allow such an input.
Spotted visually while investigating PR64268. Tested etc.; okay for
mainline?
Segher
2014-12-15 Segher Boessenkool
Use of `%s' in diagnostics is long obsoleted by %qs (in this case, using
%qE with the identifier directly, rather than using IDENTIFIER_POINTER, is
preferred).
Only occurrence fixed by mimicing the i386 port.
INTVAL / UINTVAL return HOST_WIDE_INT / unsigned HOST_WIDE_INT, not long /
Jan Hubicka hubi...@ucw.cz writes:
* cgraphunit.c (analyze_functions): Do not analyze extern inline
funtions when not optimizing; skip comdat locals.
FAIL: g++.dg/torture/pr60854.C -O0 (test for excess errors)
Excess errors:
/usr/local/gcc/gcc-20141215/gcc/testsuite/g++.dg
2014-12-15 11:48 GMT+01:00 Paolo Carlini paolo.carl...@oracle.com:
... committed as obvious the below.
Paolo.
/
Thanks
Kai
m68k revealed another missing check before TYPE_OVERFLOW_WRAPS.
I think we should use INTEGRAL_TYPE_P, and not ANY_INTEGRAL_TYPE_P
because the switch handles VECTOR_CST and COMPLEX_CST.
Bootstrapped/regtested on x86_64-linux and ppc64-linux, ok for trunk?
2014-12-15 Marek Polacek
Use 32-bit instructions only since currenlty there is no demand for a
larger address space. Provide one multilib with FPU and AltiVec support
and one without.
This patch should be applied to GCC 4.9 and mainline. I do not have
write access, so in case this gets approved, please commit it for
GCC generates SPE instructions even if -msoft-float is specified.
Explicitly add -mno-spe to prevent generation of SPE instructions. This
multilib variant must not lead to a usage of the SPE.
This patch should be applied to GCC 4.9 and mainline. I do not have
write access, so in case this gets
This patch should be applied to GCC 4.9 and mainline. I do not have
write access, so in case this gets approved, please commit it for me.
gcc/ChangeLog
2014-12-15 Sebastian Huber sebastian.hu...@embedded-brains.de
* config/rs6000/t-rtems: Use MULTILIB_REQUIRED instead of
On Mon, 15 Dec 2014, Marek Polacek wrote:
m68k revealed another missing check before TYPE_OVERFLOW_WRAPS.
I think we should use INTEGRAL_TYPE_P, and not ANY_INTEGRAL_TYPE_P
because the switch handles VECTOR_CST and COMPLEX_CST.
Bootstrapped/regtested on x86_64-linux and ppc64-linux, ok for
On Mon, Nov 17, 2014 at 05:35:23PM +, Kyrill Tkachov wrote:
Hi all,
This patch implements the vsqrt_f64 intrinsic in arm_neon.h.
There's not much to it, we can reuse __builtin_sqrt.
It's a fairly straightforward and self-contained patch,
do we still want it at this stage?
A new
Use 32-bit instructions only since currenlty there is no demand for a
larger address space. Provide one multilib with FPU and AltiVec support
and one without.
This patch should be applied to GCC 4.9 and mainline. I do not have
write access, so in case this gets approved, please commit it for
The following robustifies mark_loop_for_removal against multiple
invocations on the same loop.
Bootstrapped and tested on x86_64-unknown-linux-ngu, applied.
Richard.
2014-12-15 Richard Biener rguent...@suse.de
PR middle-end/64246
* cfgloop.c (mark_loop_for_removal): Make
On Mon, 15 Dec 2014, Prathamesh Kulkarni wrote:
On 15 December 2014 at 02:03, Prathamesh Kulkarni
prathamesh.kulka...@linaro.org wrote:
Print name of capture in patterns written by user.
* genmatch.c
(capture::name): New.
(capture::capture): New default argument.
On Mon, 15 Dec 2014, Prathamesh Kulkarni wrote:
Caused segfault for pattern containing no captures at:
info.safe_grow_cleared(capture_max + 1); in capture_info::capture_info
artificial test-case:
(define_predicates integer_zerop)
(simplify
(bit_not integer_zerop)
{ build_zero_cst
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2014-12-15 Richard Biener rguent...@suse.de
PR middle-end/64295
* match.pd (X / CST - X * (1 / CST): Use const_binop instead of
fold_binary to compute the constant to multiply with.
*
Hi all,
here is another small diagnostic enhancement for procedure pointer
components. Regtested on x86_64-unknown-linux-gnu. Ok for trunk?
(I'm not adding a dedicated test case, since coarray_collectives_14
already includes this case as a FIXME, which I now transformed into a
dg-error.)
On 15 December 2014 at 10:56, David Sherwood david.sherw...@arm.com wrote:
-Original Message-
From: Christophe Lyon [mailto:christophe.l...@linaro.org]
Sent: 11 December 2014 13:47
To: David Sherwood
Cc: gcc-patches@gcc.gnu.org; Marcus Shawcroft; Alan Hayward; Tejas Belagod;
On 13 December 2014 at 05:06, Yangfei (Felix) felix.y...@huawei.com wrote:
Thanks for reviewing the patch. See my comments inlined:
This patch fix this two issues. Three changes:
1. vfma_f32, vfmaq_f32, vfms_f32, vfmsq_f32 are only available for
arm*-*-* target with the FMA feature,
Janus Weil wrote:
here is another small diagnostic enhancement for procedure pointer
components. Regtested on x86_64-unknown-linux-gnu. Ok for trunk?
Looks good to me. Thanks for the patch!
Tobias
2014-12-15 Janus Weil ja...@gcc.gnu.org
PR fortran/63727
* resolve.c
Hi,
After this commit, GCC build fails for ARM targets:
--target=arm-none-eabi --with-mode=arm --with-cpu=cortex-a9 --with-fpu=neon
/obj-arm-none-eabi/gcc1/./gcc/xgcc -B/obj-arm-none-eabi/gcc1/./gcc/
-B/tools/arm-none-eabi/bin/ -B/tools/arm-none-eabi/lib/ -isystem
/tools/arm-none-eabi/include
On Mon, Dec 15, 2014 at 6:11 AM, Segher Boessenkool
seg...@kernel.crashing.org wrote:
If an addic. is split to addi+cmp (because RA didn't give it CR0), it will
do the wrong thing if the input reg is GPR0 (addi X,0,N is li X,N).
So don't allow such an input.
Spotted visually while
On 12/14/2014 06:14 PM, Jan Hubicka wrote:
DECL_EXTERNAL (decl) !DECL_NOT_REALLY_EXTERN (decl)
This is DECL_REALLY_EXTERN. OK with that change (in both places).
Jason
OK.
Jason
On 2014-12-15 9:14 AM, Christophe Lyon wrote:
Hi,
After this commit, GCC build fails for ARM targets:
--target=arm-none-eabi --with-mode=arm --with-cpu=cortex-a9 --with-fpu=neon
full bug report,
Can you have a look?
Sure. Sorry for inconvenience. LRA/reload bug fixing is a complicated
On 04/12/14 19:32, Jiong Wang wrote:
On 04/12/14 11:07, Richard Biener wrote:
On Thu, Dec 4, 2014 at 12:07 PM, Richard Biener
richard.guent...@gmail.com wrote:
On Thu, Dec 4, 2014 at 12:00 PM, Jiong Wang jiong.w...@arm.com wrote:
which means re-associate the constant imm with the virtual
On 15/12/14 15:28, Jiong Wang wrote:
On 04/12/14 19:32, Jiong Wang wrote:
On 04/12/14 11:07, Richard Biener wrote:
On Thu, Dec 4, 2014 at 12:07 PM, Richard Biener
richard.guent...@gmail.com wrote:
On Thu, Dec 4, 2014 at 12:00 PM, Jiong Wang jiong.w...@arm.com wrote:
which means
from the discussion here
https://gcc.gnu.org/ml/gcc-patches/2014-11/msg01949.html
the other problem it exposed is the unnecessary clobber of register x19
which
is a callee-saved register, then there are unnecessary push/pop in
pro/epilogue.
the reason comes from the following pattern:
On 15/12/2014 12:05, Segher Boessenkool wrote:
If combine is given a parallel I2, it splits it into separate I1 and
I2 insns in some cases (one case since the beginning of time; more
cases since my r218248). It gives the new I1 the same UID as the I2
already has; there is a comment that
2014-12-15 14:49 GMT+01:00 Tobias Burnus tobias.bur...@physik.fu-berlin.de:
Janus Weil wrote:
here is another small diagnostic enhancement for procedure pointer
components. Regtested on x86_64-unknown-linux-gnu. Ok for trunk?
Looks good to me. Thanks for the patch!
Thanks for the review.
Ping for https://gcc.gnu.org/ml/gcc-patches/2014-12/msg00058.html.
On 12/01/2014 05:40 PM, Pierre-Marie de Rodat wrote:
While I agree this might trigger compatibility issues with old
debuggers, I don't know what to do assuming this change is not
acceptable: should we add a kludge in
On Mon, Dec 15, 2014 at 05:21:07PM +0100, Pierre-Marie de Rodat wrote:
Ping for https://gcc.gnu.org/ml/gcc-patches/2014-12/msg00058.html.
Ok for trunk then.
On 12/01/2014 05:40 PM, Pierre-Marie de Rodat wrote:
While I agree this might trigger compatibility issues with old
debuggers, I don't
On Mon, Dec 15, 2014 at 04:51:14PM +0100, Paolo Bonzini wrote:
Random questions:
1) did you check that it never triggers on e.g. an x86 bootstrap, and
that it doesn't trigger too often on PPC64?
I have checked on my largish connection of tests for the carry insns
on PowerPC, and only two
On Mon, 15 Dec 2014, Jan Hubicka wrote:
Hi, actually this patch break fortran, I get streaming error in: lto1:
internal compiler error: in streamer_get_pickled_tree apparently picking
error_mark_node for variable constructor results in reading
integer_type...
?
Probably the
The gofrontend parser had a bug that caused it to fail to parse a
select case like *v, *ok = -c, in which the receivers of the channel
were expressions rather than identifiers. This patch from Chris
Manghane fixes the problem. This is GCC PR 61253. Bootstrapped and
ran Go testsuite on
On Mon, Dec 15, 2014 at 9:29 AM, Uros Bizjak ubiz...@gmail.com wrote:
The enclosed testcase fails on x86 when compiled with -Os since we pass
a byte parameter with a byte load in caller and read it as an int in
callee. The reason it only shows up with -Os is x86 backend encodes
a byte
Hello!
Attached patch fixes PR 68323, where code tries to access what
compiler think is out of bounds element.
2014-12-15 Uros Bizjak ubiz...@gmail.com
PR libgcc/63832
* crtstuff.c (__do_global_dtors_aux) [HIDDEN_DTOR_LIST_END]: Use
func_ptr *dtor_list temporary variable to avoid
The Go frontend converts recover calls to add an argument passed down
to the middle end. In some cases a recover call would be type checked
even after that argument is added, causing an incorrect error. This
patch from Chris Manghane fixes the problem. This is GCC PR 61248.
Bootstrapped and ran
On Mon, Dec 15, 2014 at 06:25:04PM +0100, Uros Bizjak wrote:
Hello!
Attached patch fixes PR 68323, where code tries to access what
compiler think is out of bounds element.
2014-12-15 Uros Bizjak ubiz...@gmail.com
PR libgcc/63832
* crtstuff.c (__do_global_dtors_aux)
This patch implements the last remaining language feature for C++14,
global sized deallocation. C++ has always had sized deallocation at
class scope, but didn't for deletes that use the global operator delete.
The support can be controlled separately from the -std level with the
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2014-12-15 Richard Biener rguent...@suse.de
PR tree-optimization/64312
* tree-ssa-sccvn.c (vn_reference_lookup_pieces): Use
vuse_ssa_val as callback to walk_non_aliased_vuses.
Hi!
This patch fixes ICE when cmp_mode is some vector mode, creating
comparison of a vector with scalar const0_rtx is a bad idea.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2014-12-15 Jakub Jelinek ja...@redhat.com
PR rtl-optimization/64316
*
Hi!
This PR got fixed some time ago, this patch adds a testcase for it.
2014-12-15 Jakub Jelinek ja...@redhat.com
PR rtl-optimization/63804
* gcc.dg/pr63804.c: New test.
--- gcc/testsuite/gcc.dg/pr63804.c.jj 2014-12-15 17:35:31.978451234 +0100
+++
On Sat, Aug 23, 2014 at 06:59:14PM +0200, Paul Richard Thomas wrote:
Dear Steven,
I am constantly amazed that data statement bugs keep turning up:-)
Anyway, your fix is fine for trunk and, if you feel so inclined, 4.8
and 4.9.
Steven didn't respond to my ping about this PR, so I've updated
Hi!
As discussed in the PR, to support exceptions in -fsanitize=thread code,
it is desirable to call __tsan_func_exit also when leaving functions by
means of exceptions.
Adding EH too late sounds too hard to me, so this patch instead adds an
internal call during gimplification, makes sure the
My last patch for PR64110 results in LRA crash on ARM on compilation
of some programs. There is no PR for it. Here is the patch fixing the
occurred problem.
The patch was tested and bootstrapped on x86/x86-64 and ARM.
Committed as rev. 218760.
2014-12-15 Vladimir Makarov
Hi all,
here is a regression fix for a problem with the NON_OVERRIDABLE
attribute. For non-overridable type-bound procedures we do not have to
generate a call to the vtable, but can just translate it to a simple
('non-virtual') function call. In this particular case, an additional
generic binding
On December 15, 2014 7:39:52 PM CET, Jakub Jelinek ja...@redhat.com wrote:
Hi!
This patch fixes ICE when cmp_mode is some vector mode, creating
comparison of a vector with scalar const0_rtx is a bad idea.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
OK
Thanks,
Richard.
The following patch fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62642
The patch was successfully bootstrapped on x86-64.
It is difficult for me to make a testcase to check the right code
generation. So the patch has no test.
Committed as rev. 218761.
2014-12-15 Vladimir
On 12/15/2014 03:42 AM, Dominik Vogt wrote:
On Fri, Dec 12, 2014 at 10:14:21AM -0800, Richard Henderson wrote:
On 12/12/2014 04:06 AM, Dominik Vogt wrote:
I'm not sure I've posted the missing patch anywhere yet, so it's
attached to this message. At the moment it enables
FFI_TYPE_COMPLEX only
2014-12-15 Jakub Jelinek ja...@redhat.com
PR rtl-optimization/64316
* simplify-rtx.c (simplify_relational_operation_1): For
(eq/ne (and x y) x) and (eq/ne (and x y) y) optimizations use
CONST0_RTX instead of const0_rtx.
* gcc.dg/pr64316.c: New test.
OK,
In this testcase the problem was that we end up with a non-ref-qualified
type which has a ref-qualified TYPE_CANONICAL because the middle-end
check_qualified_type doesn't know about ref-qualifiers. So
apply_memfn_quals needs to set it up on TYPE_CANONICAL as well.
Tested x86_64-pc-linux-gnu,
Copying a call expression has to copy the state of whether varargs
have been lowered. Otherwise the compiler can crash on valid code
like *f() += 1 when f is a varargs function. This patch from Chris
Manghane fixes the problem. This is GCC PR 61255. Bootstrapped and
ran Go testsuite on
What do you think we should relax it to though? Obviously there's a balance
here between relaxing things enough and not relaxing them too far (so that
the EImode AArch64 thing I mentioned is still a noisy failure, for
example). ISTM the patch deals with the only significant case that is
Bin.Cheng wrote:
do we have some compilation time benchmarks for GCC?
I'm using the llvm test-suite to see compile time differences:
$ git clone http://llvm.org/git/test-suite.git /path/to/test-suite
$ /path/to/test-suite/configure --without-llvmsrc --without-llvmobj
Hello!
2014-12-15 Uros Bizjak ubiz...@gmail.com
* config/i386/gnu-user.h (TARGET_CAN_SPLIT_STACK): Move from here ...
* config/i386/gnu-user64.h (TARGET_CAN_SPLIT_STACK): ... and here ...
* config/i386/gnu-user-common.h (TARGET_CAN_SPLIT_STACK): ... to here.
Bootstrapped and
Richard Biener wrote:
On the llvm test-suite, I have seen one ICE with my fsm jump-thread
patch.
This patch fixes the problem:
diff --git a/gcc/tree-ssa-threadupdate.c
b/gcc/tree-ssa-threadupdate.c
index 12f83ba..f8c736e 100644
--- a/gcc/tree-ssa-threadupdate.c
+++
If no --with-cpu is specified at configure time gcc/config.gcc sets the
cpu option in configure_default_options to `v9' in sparc64 targets.
This leads to the usage of the following spec by the driver:
%{!m32:%{!mcpu=*:-mcpu=v9}}
Which in turn triggers the usage of -Av9 by default when
Eric Botcazou ebotca...@adacore.com writes:
What do you think we should relax it to though? Obviously there's a balance
here between relaxing things enough and not relaxing them too far (so that
the EImode AArch64 thing I mentioned is still a noisy failure, for
example). ISTM the patch deals
On Mon, 15 Dec 2014, Jan Hubicka wrote:
Hi, actually this patch break fortran, I get streaming error in: lto1:
internal compiler error: in streamer_get_pickled_tree apparently picking
error_mark_node for variable constructor results in reading
integer_type...
?
Probably the
Jan Hubicka hubi...@ucw.cz writes:
* cgraphunit.c (analyze_functions): Do not analyze extern inline
funtions when not optimizing; skip comdat locals.
FAIL: g++.dg/torture/pr60854.C -O0 (test for excess errors)
Excess errors:
/usr/local/gcc/gcc-20141215/gcc/testsuite/g++.dg
Hi,
avoid crashing later in build_this_parm during error recovery. Tested
x86_64-linux.
Thanks,
Paolo.
//
/cp
2014-12-15 Paolo Carlini paolo.carl...@oracle.com
PR c++/58650
* decl.c (grokdeclarator): Avoid crashing on an initialized
non-static data
This patch is a follow up to
https://gcc.gnu.org/ml/gcc-patches/2014-12/msg01068.html and converts
more flags to the common diagnostic handing. I think the rest can only
be converted by modifiying the *.opt syntax, but I might be wrong.
The patch is relative to the Fortran-part approved patch
The following patch fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63397
The patch was successfully bootstrapped on x86-64.
Committed as rev. 218766.
2014-12-15 Vladimir Makarov vmaka...@redhat.com
PR rtl-optimization/63397
* ira-int.h (ira_overall_cost, ira_reg_cost,
Why does error recovery fail? I would expect to be able to just drop
the 'friend' and treat it as a normal non-static data member.
Jason
Hi,
this is final version I comitted. 20110201-1_0.c actually tests that we
optimize cabs on function copmiled with -O0 that is no longer supposed to
happen.
Honza
PR lto/64043
* gcc.dg/lto/20110201-1_0.c: New testcase.
* tree-streamer.c (preload_common_nodes): Skip
This weekend I was running GDB's testsuite with many options enabled,
and I noticed that, for some specific configurations (specifically
when testing gdbserver), I was getting the following error:
dg-extract-results.sh: sum files are for multiple tools, specify a tool
I remembered seeing this a
The code that this macro enables will never do anything anyway on
RL78. Applied.
2014-12-15 DJ Delorie d...@redhat.com
* config/rl78/rl78.h: Remove SHORT_IMMEDIATES_SIGN_EXTEND.
Index: config/rl78/rl78.h
===
---
On Mon, Dec 15, 2014 at 05:37:03PM -0500, Sergio Durigan Junior wrote:
2014-12-14 Sergio Durigan Junior sergi...@redhat.com
* dg-extract-results.sh: Pass '--text' option to grep when
filtering .{sum,log} files, which may contain binary data.
I'd be surprised if all versions of
On Monday, December 15 2014, Jakub Jelinek wrote:
I'd be surprised if all versions of grep supported --text option (e.g. POSIX
doesn't mention the -a nor --text options), guess
you'd need to check for that first (early in the script) and add it only if
it works.
Thanks for the review, Jakub.
From: Eric Botcazou ebotca...@adacore.com
Date: Mon, 15 Dec 2014 22:27:38 +0100
I think it would be reasonable to have gcc targetting ultrasparc
extensions by default in sparc64-*-linux*. WDYT?
No strong opinion. FreeBSD and OpenBSD already do it so why not?
DaveM, any opinion?
Keep in
I've merged GCC trunk to the gccgo branch, again.
Ian
Hi,
This commit will cause another GCC build fail for ARM targets. The details are
descripted in the following Bugzilla linker:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64323.
Could you help me to have a look?
Thanks,
Hale.
-Original Message-
From: gcc-patches-ow...@gcc.gnu.org
Hi, all,
In nds32 port, there is a wrong design in casesi_internal pattern.
Since clobber always discards the previous value, it should have
constraint modifier '=' so that LRA is able to correctly handle the
register live info.
So we have this patch to fix the issue. Committed as Rev.218774.
Hi Janus, hi all,
Janus Weil wrote:
here is a regression fix for a problem with the NON_OVERRIDABLE
attribute. For non-overridable type-bound procedures we do not have to
generate a call to the vtable, but can just translate it to a simple
('non-virtual') function call. In this particular case,
96 matches
Mail list logo
