On Fri, May 06, 2016 at 02:14:31PM +0800, Marcel Böhme wrote:
> * the stack overflow reported in PR68159 in cplus_demangle_print_callback,
> * a potential stack overflow in d_demangle_callback
> * a potential stack overflow in is_ctor_or_dtor, and
> * six potential buffer overflows (initialise less
It's already done by fwprop_done.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2016-05-06 Richard Biener
* fwprop.c (fwprop): Remove duplicate cleanup_cfg call.
(fwprop_addr): Likewise.
Index: gcc/fwprop.c
=
The following makes us skip zero-sized fields when encoding
aggregate constructors to avoid ICEing when recursing with size == 0.
Bootstrapped and tested on x86_64-unknown-linux-gnu, ok?
Thanks,
Richard.
2016-05-06 Richard Biener
PR middle-end/70931
* dwarf2out.c (native_enc
On Fri, May 06, 2016 at 09:35:18AM +0200, Richard Biener wrote:
>
> The following makes us skip zero-sized fields when encoding
> aggregate constructors to avoid ICEing when recursing with size == 0.
>
> Bootstrapped and tested on x86_64-unknown-linux-gnu, ok?
Ok (looks safe even for the branch)
The following completes the fix for PR67921 now that we have a testcase
for the non-pointer case.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2016-05-06 Richard Biener
PR middle-end/70941
* fold-const.c (split_tree): Always convert to the original
Hi Jakub,
The patch that is attached now is bootstrapped and regression tested on
x86_64-pc-linux-gnu.
>
> This file is used not just in the various tools like binutils or gdb, but
> also in libstdc++, where it used e.g. in the std::terminate handler,
> which I think can't just xmalloc_failed,
Hi.
Honza asked me to explain the change more verbosely.
The patch simplify enhances verbose dump of IVOPTS so that
# of iterations is printed. Apart from that it also prints
invariant expression that are used during the algorithm which
considers a set of candidates which is improved.
Main motiv
A program containing an array of structs containing a VLA caused ICE with UBSAN
bounds checking, because in get_ubsan_type_info_for_type we asserted that the
size of a type fits uhwi, which implies it is an INTEGER_CST. But that's not
the case for a struct with VLA. However, the assert here is bo
On Fri, May 06, 2016 at 11:22:41AM +0200, Marek Polacek wrote:
> A program containing an array of structs containing a VLA caused ICE with
> UBSAN
> bounds checking, because in get_ubsan_type_info_for_type we asserted that the
> size of a type fits uhwi, which implies it is an INTEGER_CST. But th
On Fri, May 06, 2016 at 11:29:33AM +0200, Jakub Jelinek wrote:
> On Fri, May 06, 2016 at 11:22:41AM +0200, Marek Polacek wrote:
> > A program containing an array of structs containing a VLA caused ICE with
> > UBSAN
> > bounds checking, because in get_ubsan_type_info_for_type we asserted that
> >
Updated version of the patch described below. Apart from fixing a
bug and adding a test, the new logic is now used always, for all
targets. The discussion of the original patch starts here:
https://gcc.gnu.org/ml/gcc-patches/2015-11/msg03052.html
The new patch has been bootstrapped and regressi
On Tue, May 3, 2016 at 11:08 AM, Richard Biener
wrote:
> On Tue, May 3, 2016 at 12:01 PM, Bin.Cheng wrote:
>> On Mon, May 2, 2016 at 10:00 AM, Richard Biener
>> wrote:
>>> On Fri, Apr 29, 2016 at 5:05 PM, Bin.Cheng wrote:
On Fri, Apr 29, 2016 at 12:16 PM, Richard Biener
wrote:
>
On Fri, May 6, 2016 at 10:40 AM, Bin.Cheng wrote:
> On Tue, May 3, 2016 at 11:08 AM, Richard Biener
> wrote:
>> On Tue, May 3, 2016 at 12:01 PM, Bin.Cheng wrote:
>>> On Mon, May 2, 2016 at 10:00 AM, Richard Biener
>>> wrote:
On Fri, Apr 29, 2016 at 5:05 PM, Bin.Cheng wrote:
> On Fri,
> diff --git a/gcc/cfgexpand.c b/gcc/cfgexpand.c
> index 21f21c9..4d48afd 100644
> --- a/gcc/cfgexpand.c
> +++ b/gcc/cfgexpand.c
...
> @@ -1099,8 +1101,10 @@ expand_stack_vars (bool (*pred) (size_t), struct
> stack_vars_data *data)
>
>/* If there were any, allocate space. */
>if
Hi,
The attached patch adds another combine pattern variant for the SH
rotcr instruction.
Tested on sh-elf with
make -k check RUNTESTFLAGS="--target_board=sh-sim\{-m2/-ml,-m2/-mb,
-m2a/-mb,-m4/-ml,-m4/-mb,-m4a/-ml,-m4a/-mb}"
Committed as r235950.
Cheers,
Oleg
gcc/ChangeLog:
PR target/
On Fri, May 06, 2016 at 05:01:14PM +0800, Marcel Böhme wrote:
> The patch that is attached now is bootstrapped and regression tested on
> x86_64-pc-linux-gnu.
>
> >
> > This file is used not just in the various tools like binutils or gdb, but
> > also in libstdc++, where it used e.g. in the std:
Hi,
The attached patch addresses some of the remaining things as mentioned
in the PR.
Tested on sh-elf with
make -k check RUNTESTFLAGS="--target_board=sh-sim\{-m2/-ml,-m2/-mb,
-m2a/-mb,-m4/-ml,-m4/-mb,-m4a/-ml,-m4a/-mb}"
Committed as r235952.
Cheers,
Oleg
gcc/ChangeLog:
PR target/5293
Hi!
With 32 OpenMP clauses and 27 further OpenACC ones, I can't add 10 further
clauses I need for OpenMP.
So, this patch implements using C++ classes a framework where the code
can use mostly what it used, yet it is now up to 128 bits, while being not
really more expensive at -O2 than passing two
On 11/26/2015 10:04 PM, Bernd Schmidt wrote:
> As I said previously, the one to just replace whitespace is ok for now.
> Please ping the other one when stage1 opens (I expect it'll need changes by
> then).
>
>
> Bernd
Hello.
This part of the part remains to be installed from the previous stag
Hi.
I've spotted couple of occurrences of following memory leak seen by valgrind:
malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
operator new(unsigned long) (new_op.cc:50)
remap_dependence_clique(copy_body_data*, unsigned short) (tree-inline.c:845)
remap_gimple_op_r(tre
The following fixes $subject.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2016-05-06 Richard Biener
PR tree-optimization/70960
* tree-if-conv.c (ifcvt_walk_pattern_tree): Handle non-SSA ops.
* gfortran.fortran-torture/compile/pr70960.f90:
Hi,
The attached patch fixes PR 58219.
Tested on sh-elf with
make -k check RUNTESTFLAGS="--target_board=sh-sim\{-m2/-ml,-m2/-mb,
-m2a/-mb,-m4/-ml,-m4/-mb,-m4a/-ml,-m4a/-mb}"
Committed as r235954.
gcc/ChangeLog:
PR target/58219
* config/sh/predicates.md (long_displacement_mem_op
Hi,
The attached patch removes some workaround combine patterns. As far as
I remember this issue has been addressed by some match.pd patterns. In
any case, CSiBE code size shows no difference and the SH specific
testcases mentioned in the code pass without the patterns.
Tested on sh-elf with
m
On Wed, May 4, 2016 at 7:25 PM, Nathan Sidwell wrote:
> This patch fixes an ICE Thomas observed in tree-ssa-tail-merge.c:
>
> On 05/03/16 06:34, Thomas Schwinge wrote:
>
>> I'm also seeing the following regression for C and C++,
>> libgomp.oacc-c-c++-common/loop-auto-1.c with -O2:
>>
>> source
On Wed, May 4, 2016 at 10:49 PM, David Malcolm wrote:
> The RTL frontend needs to be able to lookup passes by name.
>
> passes.c has global state name_to_pass_map (albeit static, scoped
> to passes.c), for use by enable_disable_pass.
>
> Move it to be a field of class pass_manager, and add
> a get
On Wed, May 4, 2016 at 10:49 PM, David Malcolm wrote:
> This patch makes the argv param to read_md_files const, needed
> so that the RTL frontend can call it on a const char *.
>
> While we're at it, it similarly makes const the argv for all
> of the "main" functions of the various gen*.
>
> OK fo
On Wed, May 4, 2016 at 10:49 PM, David Malcolm wrote:
> In order to faithfully load RTL dumps that contain references to
> source locations, the RTL frontend needs to be able to parse file
> and line information and turn then into location_t values.
>
> Unfortunately, the libcpp API makes it rathe
Hi,
The attached patch fixes the length of the ic_invalidate_line_sh4a
pattern.
Tested on sh-elf with
make -k check RUNTESTFLAGS="--target_board=sh-sim\{-m2/-ml,-m2/-mb,
-m2a/-mb,-m4/-ml,-m4/-mb,-m4a/-ml,-m4a/-mb}"
Committed as r235957.
Cheers,
Oleg
gcc/ChangeLog:
* config/sh/sh.md (i
On Thu, May 5, 2016 at 4:19 PM, Richard Sandiford
wrote:
> wide_int_constant_multiple_p used:
>
> if (*mult_set && mult != 0)
> return false;
>
> to check whether we had previously seen a nonzero multiple, but "mult" is
> a pointer to the previous value rather than the previous value
On Thu, May 5, 2016 at 5:08 PM, Eric Botcazou wrote:
> Hi,
>
> gimple_can_coalesce_p is rather picky about the conditions under which SSA
> names can be coalesced. In particular, when it comes to the type, it's:
>
> /* Now check the types. If the types are the same, then we should
> try t
On Thu, May 5, 2016 at 5:19 PM, Yuri Rumyantsev wrote:
> Hi All,
>
> Here is a simple patch which cures the problem with nonlegal
> transformation of endless loop. THe fix is simply check that guard
> edge destination is not loop latch block.
>
> Bootstrapping and regression testing did not show a
On Fri, May 6, 2016 at 12:06 PM, Martin Liška wrote:
> On 11/26/2015 10:04 PM, Bernd Schmidt wrote:
>> As I said previously, the one to just replace whitespace is ok for now.
>> Please ping the other one when stage1 opens (I expect it'll need changes by
>> then).
>>
>>
>> Bernd
>
> Hello.
>
> Th
On Fri, May 6, 2016 at 12:10 PM, Martin Liška wrote:
> Hi.
>
> I've spotted couple of occurrences of following memory leak seen by valgrind:
>
> malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
> operator new(unsigned long) (new_op.cc:50)
> remap_dependence_clique(copy_body_
Hello.
I've started working on the patch couple of month go, basically after
a brief discussion with Jakub on IRC.
I'm sending the initial version which can successfully run instrumented
tramp3d, postgresql server and Inkscape. It catches the basic set of
examples which are added in following pat
Hi,
The attached patch removes some deprecated SH options.
Tested on sh-elf with 'make all-gcc' and with 'make info dvi pdf'.
Committed as r235960.
Cheers,
Oleg
gcc/ChangeLog:
* config/sh/sh.opt (madjust-unroll, minvalid-symbols, msoft-atomic,
mspace): Remove deprecated options.
Hi.
This is a new test coverage for the new sanitizer option.
Martin
>From 753bfb3edb12c9f3fd13f320e308556f63330c97 Mon Sep 17 00:00:00 2001
From: marxin
Date: Wed, 4 May 2016 12:57:05 +0200
Subject: [PATCH 2/2] Introduce tests for -fsanitize=use-after-scope
gcc/testsuite/ChangeLog:
2016-05-04
Hello.
One more issue I forgot to mention in the previous email:
e) As one can come up with a source code which jumps to a label within
a block scope (use-after-scope-goto-1.c):
// { dg-do run }
// { dg-additional-options "-fsanitize=use-after-scope -fstack-reuse=none" }
int main(int argc, char
The following patch fixes another case of missing DECL_EXPR in the FE.
Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
Ok for trunk?
Thanks,
Richard.
2016-05-06 Richard Biener
PR fortran/70937
* trans-decl.c (gfc_trans_vla_type_sizes): Add a DECL_EXPR for
Robert Suchanek writes:
> I'm resending this patch as it has been rebased and updated. I reverted
> a change to check_effective_target_vect_call_lrint procedure because it
> does not use cached result.
Conceptually I think this is a good idea and to the extent that I can
follow TCL code it looks
On Fri, 6 May 2016, Richard Biener wrote:
>
> The following patch fixes another case of missing DECL_EXPR in the FE.
>
> Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
>
> Ok for trunk?
Dominique noticed a FAIL early which is fixed by adjusting the patch
to only handle TYPE_DEC
On 04 May 21:35, Jakub Jelinek wrote:
> Hi!
>
> Not sure how to easily construct a testcase for this (these insns are
> usually used for vectorization, and then it really depends on register
> pressure).
> But in any case, looking at documentation it seems all the used insns are
> available (gener
On 04 May 21:37, Jakub Jelinek wrote:
> Hi!
>
> Another pair of define_insns where all the VEX insns have EVEX variant
> in AVX512VL.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
OK for trunk.
--
Thanks, K
>
> 2016-05-04 Jakub Jelinek
>
> * config/i386/sse.
On 04 May 21:43, Jakub Jelinek wrote:
> Hi!
>
> This patch tweaks more define_insns at once, again all the insns
> should be already in AVX512F or AVX512VL.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
OK for trunk.
--
Thanks, K
>
> 2016-05-04 Jakub Jelinek
>
>
On 04 May 21:41, Jakub Jelinek wrote:
> Hi!
>
> Another 3 define_insns that can handle xmm16+ operands.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
OK for trunk.
--
Thanks, K
>
> 2016-05-04 Jakub Jelinek
>
> * config/i386/sse.md (vec_interleave_lowv4sf,
>
On 05/06/2016 02:04 PM, Martin Liška wrote:
Hello.
I've started working on the patch couple of month go, basically after
a brief discussion with Jakub on IRC.
I'm sending the initial version which can successfully run instrumented
tramp3d, postgresql server and Inkscape. It catches the basic se
On 04 May 21:44, Jakub Jelinek wrote:
> Hi!
>
> Another pair of define_insns.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
OK for trunk.
--
Thanks, K
>
> 2016-05-04 Jakub Jelinek
>
> * config/i386/sse.md (*vec_concatv2sf_sse4_1, *vec_concatv4sf): Use
>
On 04 May 21:48, Jakub Jelinek wrote:
> Hi!
>
> As the testcase shows, we unnecessarily disallow xmm16+, even when
> we can use them for -mavx512bw.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
OK for trunk.
--
Thanks, K
>
> 2016-05-04 Jakub Jelinek
>
> * c
On 04 May 21:47, Jakub Jelinek wrote:
> Hi!
>
> While EVEX doesn't have vextracti128, we can use vextracti32x4;
> unfortunately without avx512dq we need to use full zmm input operand,
> but that shouldn't be a big deal when we hardcode 1 as immediate.
>
> Bootstrapped/regtested on x86_64-linux an
On 04 May 21:51, Jakub Jelinek wrote:
> Hi!
>
> In this case the situation is more complicated, because for
> V*HI we need avx512bw and avx512vl, while for V*SI only avx512vl
> is needed and both are in the same pattern. But we already have
> a pattern that does the right thing right after the "a
On Tue, 3 May 2016, Richard Biener wrote:
On Tue, May 3, 2016 at 3:26 PM, Marc Glisse wrote:
On Tue, 3 May 2016, Richard Biener wrote:
On Tue, May 3, 2016 at 8:36 AM, Marc Glisse wrote:
This removes the duplication. I also removed the case (A&B)&(A&C) which
is
handled by reassoc. And I ne
On 04 May 21:53, Jakub Jelinek wrote:
> Hi!
>
> AVX512BW has EVEX insns for these.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
OK for trunk.
--
Thanks, K
>
> 2016-05-04 Jakub Jelinek
>
> * config/i386/sse.md (*v8hi3, *v16qi3): Add
> avx512bw alternat
On Fri, May 06, 2016 at 01:04:30PM +0200, Martin Liška wrote:
> I've started working on the patch couple of month go, basically after
> a brief discussion with Jakub on IRC.
>
> I'm sending the initial version which can successfully run instrumented
> tramp3d, postgresql server and Inkscape. It ca
The following fixes PR70948, a failure of PTA considering all
fields of va_list being clobbered (assigned from NONLOCAL) for
__builtin_va_start. With the new pointer-vs.-decl comparison
optimization this bug manifests as a miscompile of
gcc.c-torture/execute/va-arg-pack-1.c on AARCH64.
Bootstrap
On 05/06/2016 12:56 PM, Richard Biener wrote:
> Hmmm. But this means debug stmt remapping calls
> remap_dependence_clique which may end up bumping
> cfun->last_clique and thus may change code generation.
>
> So what debug stmts contain MEM_REFs? If you put an assert
> processing_debug_stmt == 0
On Fri, May 06, 2016 at 02:48:30PM +0300, Yury Gribov wrote:
> >6) As the use-after-scope stuff is already included in libsanitizer, no
> >change is needed for the library
>
> Note that upstream seems to use a different cmdline interface. They don't
> have a dedicated -fsanitize=use-after-scope a
On 05/03/2016 11:07 AM, Bin.Cheng wrote:
> Patch applied as suggested at r235808.
>
> Thanks,
> bin
Hi.
Following patch introduces memory leak:
/home/marxin/Programming/gcc2/objdir/gcc/xgcc
-B/home/marxin/Programming/gcc2/objdir/gcc/-fno-diagnostics-show-caret
-fdiagnostics-color=never
On Fri, May 6, 2016 at 2:40 PM, Martin Liška wrote:
> On 05/03/2016 11:07 AM, Bin.Cheng wrote:
>> Patch applied as suggested at r235808.
>>
>> Thanks,
>> bin
>
> Hi.
>
> Following patch introduces memory leak:
> /home/marxin/Programming/gcc2/objdir/gcc/xgcc
> -B/home/marxin/Programming/gcc2/objdi
On 05/06/2016 02:38 PM, Jakub Jelinek wrote:
> On Fri, May 06, 2016 at 02:48:30PM +0300, Yury Gribov wrote:
>>> 6) As the use-after-scope stuff is already included in libsanitizer, no
>>> change is needed for the library
>>
>> Note that upstream seems to use a different cmdline interface. They don
On 05/06/16 08:35, David Wohlferd wrote:
> On 5/5/2016 10:29 AM, Bernd Edlinger wrote:
>> Hi!
>>
>> this patch is inspired by recent discussion about basic asm:
>>
>> Currently a basic asm is an instruction scheduling barrier,
>> but not a memory barrier, and most surprising, basic asm
>> does _not
On 05/06/2016 01:48 PM, Yury Gribov wrote:
> On 05/06/2016 02:04 PM, Martin Liška wrote:
>> Hello.
>>
>> I've started working on the patch couple of month go, basically after
>> a brief discussion with Jakub on IRC.
>>
>> I'm sending the initial version which can successfully run instrumented
>> tr
On 02/24/16 16:52, Aaron Conole wrote:
The previous gcov behavior was to always output errors on the stderr channel.
This is fine for most uses, but some programs will require stderr to be
untouched by libgcov for certain tests. This change allows configuring
the gcov output via an environment va
On Fri, May 06, 2016 at 03:17:23PM +0200, Martin Liška wrote:
> On 05/06/2016 01:48 PM, Yury Gribov wrote:
> > On 05/06/2016 02:04 PM, Martin Liška wrote:
> >> I've started working on the patch couple of month go, basically after
> >> a brief discussion with Jakub on IRC.
> >>
> >> I'm sending the
On 05/06/2016 03:38 PM, Jakub Jelinek wrote:
On Fri, May 06, 2016 at 02:48:30PM +0300, Yury Gribov wrote:
6) As the use-after-scope stuff is already included in libsanitizer, no change
is needed for the library
Note that upstream seems to use a different cmdline interface. They don't
have a d
Hi
I made the corrections to the patch.
Changelog 2016-5-6 Andres Tiraboschi
*gcc/plugin.c (PLUGIN_EVAL_CALL_CONSTEXPR): New event.
*gcc/plugin.def (PLUGIN_EVAL_CALL_CONSTEXPR): New event.
*gcc/cp/constexpr.c (constexpr_fundef): Moved to gcc/cp/constexpr.h.
*gcc/cp/constexpr.c (
Hi Jim,
On 05/05/16 22:37, Jim Wilson wrote:
For this simple testcase
double
sub (void)
{
return 0.0;
}
Without the attached patch, an ARM compiler with neon support enabled, gives
vldr.64 d0, .L2
With the attached patch, an ARM compiler with neon enabled, gives
vmov.i64 d0, #0@
This patch adds support for the signed and unsigned int versions of the
vec_addec altivec builtins from the Power Architecture 64-Bit ELF V2 ABI
OpenPOWER ABI for Linux Supplement (16 July 2015 Version 1.1). There are
many of the builtins that are missing and this is part of a series
of patches to
Hello!
2016-05-06 Uros Bizjak
* config/i386/i386.md (int cmove peephole2s): Use general_reg_operand
instead of register_and_not_any_fp_reg_operand as operand 0 predicate.
* config/i386/predicates.md (register_and_not_any_fp_reg_operand):
Remove unused predicate.
(register_a
On Fri, May 06, 2016 at 05:22:46PM +0300, Yury Gribov wrote:
> On 05/06/2016 03:38 PM, Jakub Jelinek wrote:
> >On Fri, May 06, 2016 at 02:48:30PM +0300, Yury Gribov wrote:
> >>>6) As the use-after-scope stuff is already included in libsanitizer, no
> >>>change is needed for the library
> >>
> >>No
On 05/06/2016 03:25 PM, Jakub Jelinek wrote:
> Well, we already have the gimple poisoning/unpoisoning code on RTL (emitted
> after the prologue and before the epilogue), so it shouldn't be that hard.
> I'd only do the most common/easy cases inline though, like 1/2/4/8/16/32
> bytes long variables.
Hi Jakub,
> On 6 May 2016, at 5:51 PM, Jakub Jelinek wrote:
>>
>
> If you just want an array, restricting the size including the sizeof
> to fit into int makes no sense, you want to guard it against overflows
> during the multiplication.
Okay, done. (Someone might want to substitute size_t with
On Fri, May 06, 2016 at 04:41:41PM +0200, Martin Liška wrote:
> On 05/06/2016 03:25 PM, Jakub Jelinek wrote:
> > Well, we already have the gimple poisoning/unpoisoning code on RTL (emitted
> > after the prologue and before the epilogue), so it shouldn't be that hard.
> > I'd only do the most common
On Fri, May 06, 2016 at 10:46:12PM +0800, Marcel Böhme wrote:
>d_print_init (&dpi, callback, opaque, dc);
>
> - {
> -#ifdef CP_DYNAMIC_ARRAYS
> -__extension__ struct d_saved_scope scopes[dpi.num_saved_scopes];
> -__extension__ struct d_print_template temps[dpi.num_copy_templates];
>
Currently, there are three major issues in AArch64 variable argument
(vaarg) support.
* tree-stdarg pass is not enabled, thus we are doing uncessary
register pushes/popes. This is PR63596.
* va_arg gimplification hook is generating sub-optimal code due to the
runtime boundary check
This patch initialize va_list_gpr_counter_field and
va_list_fpr_counter_field properly for AArch64 backend that tree-stdarg
pass will be enabled.
The "required register" analysis is largely target independent, but the
user might operate on the inner offset field in vaarg structure directly,
for e
This patch fixes PR63596.
There is no need to push/pop all arguments registers. We only need to
push and pop those registers used. These use info is calculated by a
dedicated vaarg optimization tree pass "tree-stdarg", the backend should
honor it's analysis result.
For a simple testcase where va
AArch64 va_arg gimplify hook is generating redundant instructions.
The current va_arg fetch logic is:
1 if (va_arg offset shows the arg is saved at reg_save_area)
2 if ((va_arg_offset + va_arg_type_size) <= 0)
3fetch va_arg from reg_save_area.
4 else
5fetch va_arg from i
Based on patch [3/4], we can further optimize the vaarg gimplification
logic, this time not for redundant checks, but for redundant basic
blocks. Thus we can simplify the control graph and eventually generate
less branch instructions.
The current gimplification logic requires three basic blocks:
Hi Robert,
Robert Suchanek writes:
> Revised patch attached.
>
> Tested with mips-img-linux-gnu and bootstrapped x86_64-unknown-linux-
> gnu.
One small tweak, ChangeLog should wrap at 74 columns. Please consider the
full list of authors for this patch as it has had many major contributors
now.
> If one malloc succeeds and the other fails, you leak memory.
>
> Jakub
Nice catch. Thanks!
Bootstrapped and regression tested on x86_64-pc-linux-gnu.
Best - Marcel
Index: libiberty/ChangeLog
===
--- libiberty/ChangeLog (re
On Fri, May 06, 2016 at 11:11:29PM +0800, Marcel Böhme wrote:
> + dpi.copy_templates
> += (struct d_print_template *) malloc (((size_t) dpi.num_copy_templates)
> + * sizeof (*dpi.copy_templates));
> + if (! dpi.copy_templates)
> +{
> + d_print_e
Robert Suchanek writes:
>
> gcc/ChangeLog:
>
> * config/mips/i6400.md (i6400_fpu_intadd, i6400_fpu_logic)
> (i6400_fpu_div, i6400_fpu_cmp, i6400_fpu_float, i6400_fpu_store)
> (i6400_fpu_long_pipe, i6400_fpu_logic_l, i6400_fpu_float_l)
> (i6400_fpu_mult): New cpu units.
>
On Fri, May 06, 2016 at 09:37:46AM +0200, Richard Biener wrote:
>
> The following completes the fix for PR67921 now that we have a testcase
> for the non-pointer case.
>
> Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
The testcase (for obvious reasons) fails on -funsigned-char de
This patch improves the auto loop partitioning algorithm in 2 ways.
1) rather than try and assign just the outer loop to the outer partition and
then all innermost loops to partitioning axis, this changes the algorithm to
assign the innermost loop to the innermost partition and then the outerm
Hi,
This patch also removes the following part of the comment for method
cplus_demangle_print_callback:
"It does not use heap memory to build an output string, so cannot encounter
memory allocation failure”.
> On 6 May 2016, at 11:11 PM, Marcel Böhme wrote:
>
>
>> If one malloc succeeds and
C++11 adds the ability to add "override" after an implementation of a
virtual function in a subclass, to:
(A) document that this is an override of a virtual function
(B) allow the compiler to issue a warning if it isn't (e.g. a mismatch
of the type signature).
Similarly, it allows us to add a "fin
Mark most virtual functions in gcc/jit as being FINAL OVERRIDE.
gcc::jit::recording::lvalue::access_as_rvalue is the sole OVERRIDE
that isn't a FINAL.
Successfully bootstrapped®rtested on x86_64-pc-linux-gnu.
I can self-approve this, but as asked in patch 1,
does "final" imply "override"? Is "fi
On Sat, May 07, 2016 at 12:05:11AM +0800, Marcel Böhme wrote:
> This patch also removes the following part of the comment for method
> cplus_demangle_print_callback:
> "It does not use heap memory to build an output string, so cannot encounter
> memory allocation failure”.
But that exactly is th
On Fri, May 6, 2016 at 2:51 AM, Jakub Jelinek wrote:
>
> Anyway, perhaps I'm misremembering, if there is a mode that really can't
> fail due to allocation failures or not, we need to deal with that.
> Ian or Jason, can all the demangle users allocate heap memory or not?
> And, if __cxa_demangle ca
On Fri, May 06, 2016 at 12:40:45PM -0400, David Malcolm wrote:
> C++11 adds the ability to add "override" after an implementation of a
> virtual function in a subclass, to:
> (A) document that this is an override of a virtual function
> (B) allow the compiler to issue a warning if it isn't (e.g. a
On Fri, 2016-05-06 at 18:20 +0200, Jakub Jelinek wrote:
> On Fri, May 06, 2016 at 12:40:45PM -0400, David Malcolm wrote:
> > C++11 adds the ability to add "override" after an implementation of
> > a
> > virtual function in a subclass, to:
> > (A) document that this is an override of a virtual funct
On Fri, May 06, 2016 at 12:32:47PM -0400, David Malcolm wrote:
> Perhaps, but CONSTEXPR seems to be more awkward than OVERRIDE and
> FINAL. The meanings of "final" and "override" are consistent between
> C++11 and C++14, but C++14 allows more things to be marked as
> "constexpr" than C++11. Hence
Allow using __attribute__((shared)) to place static variables in '.shared'
memory space.
Changes in v2:
- reword diagnostic message in nvptx_handle_shared_attribute to follow other
backends ("... attribute not allowed with auto storage class");
- reject explicit initialization of ".shared" memor
This patch by Chris Manghane implements the basic framework for the
new escape analysis. It doesn't really do anything at this point,
this is just a skeleton. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
2016-05-06 Chris Manghane
* Make-lang.in (GO_O
Hi Ville,
since you wrote the latest patches on tuple constructors, do you have an
opinion on this patch, or alternate strategies to achieve the same goal?
https://gcc.gnu.org/ml/libstdc++/2016-04/msg00041.html
On Thu, 21 Apr 2016, Marc Glisse wrote:
On Thu, 21 Apr 2016, Jonathan Wakely wr
On 05/06/2016 05:40 PM, David Malcolm wrote:
> +#if __cplusplus >= 201103
> +/* C++11 claims to be available: use it: */
> +#define OVERRIDE override
> +#define FINAL final
> +#else
> +/* No C++11 support; leave the macros empty: */
> +#define OVERRIDE
> +#define FINAL
> +#endif
> +
Is there a rea
On 05/06/2016 06:56 PM, Pedro Alves wrote:
> If building gcc as a C++11 program is supported, then it
> won't be possible to use these names as symbols for
> anything else anyway?
Just found out the above is not true. Apparently I've
been stuck in C++98 for too long... Sorry about the noise.
I
On Fri, May 06, 2016 at 07:10:33PM +0100, Pedro Alves wrote:
> On 05/06/2016 06:56 PM, Pedro Alves wrote:
>
> > If building gcc as a C++11 program is supported, then it
> > won't be possible to use these names as symbols for
> > anything else anyway?
>
> Just found out the above is not true. App
On 05/06/2016 07:33 PM, Trevor Saunders wrote:
> On Fri, May 06, 2016 at 07:10:33PM +0100, Pedro Alves wrote:
>> I like your names without the GCC_ prefix better though,
>> for the same reason of standardizing binutils-gdb + gcc
>> on the same symbols.
>
> I agree, though I'm not really sure when
On 6 May 2016 at 20:51, Marc Glisse wrote:
> Hi Ville,
>
> since you wrote the latest patches on tuple constructors, do you have an
> opinion on this patch, or alternate strategies to achieve the same goal?
>
> https://gcc.gnu.org/ml/libstdc++/2016-04/msg00041.html
I have fairly mixed feelings ab
Hi!
This patch adds parsing of most of the OpenMP 4.5 clause changes,
though doesn't do anything during resolve or later with them yet.
Missing is still depend clause parsing changes (sink and source) and
link and to clause for declare target construct.
2016-05-06 Jakub Jelinek
* gfor
1 - 100 of 110 matches
Mail list logo
