On 01/07/16 13:02, Richard Biener wrote:
On Thu, 30 Jun 2016, Kyrill Tkachov wrote:
On 28/06/16 08:54, Richard Biener wrote:
On Thu, 16 Jun 2016, Kyrill Tkachov wrote:
On 15/06/16 22:53, Marc Glisse wrote:
On Wed, 15 Jun 2016, Kyrill Tkachov wrote:
This is a respin of
https://gcc.gnu.org
Hi all:
pr69102.c use -fPIC flag in dg-options but not check is available for
target, so I add "dg-require-effective-target fpic" for it.
ChangeLog
2016-07-05 Kito Cheng
* gcc.c-torture/compile/pr69102.c: Require fpic support.
From caa51d92e620694ee1365ce0f77ac2b152662982 Mon Sep 17 00
On 4 July 2016 at 18:28, Kyrill Tkachov wrote:
> Hi Christophe,
>
>
> On 22/06/16 16:52, Christophe Lyon wrote:
>>
>> Hi,
>>
>> This is a new attempt at removing neon-testgen.ml and generated files.
>>
>> Compared to my previous version several months ago:
>> - I have recently added testcases to m
[Fixed subject to reflect patch]
Ping?
Best regards,
Thomas
On Monday 27 June 2016 17:51:34 Thomas Preudhomme wrote:
> Hi Ramana,
>
> On Wednesday 01 June 2016 10:00:52 Ramana Radhakrishnan wrote:
> > From here down to
> >
> > > -#if ((__ARM_ARCH__ > 5) && !defined(__ARM_ARCH_6M__)) \
>
ping * 2 ping https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01703.html
Thanks,
Prathamesh
On 28 June 2016 at 14:49, Prathamesh Kulkarni
wrote:
> ping https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01703.html
>
> Thanks,
> Prathamesh
>
> On 23 June 2016 at 22:51, Prathamesh Kulkarni
> wrote:
>> O
2016-07-04 22:58 GMT+03:00 Andi Kleen :
> Andi Kleen writes:
>
> PING!
>
>> From: Andi Kleen
>>
>> I have a Skylake system with MPX in the CPU, but MPX is disabled
>> in the kernel configuration.
>>
>> This makes all the MPX tests fail because they assume if MPX
>> is in CPUID it works
>>
>> Chec
On Mon, Jul 4, 2016 at 11:45 PM, Ulrich Drepper wrote:
> Anyone?
>
> On Mon, Jun 27, 2016 at 1:31 PM, Ulrich Drepper wrote:
>> The manual says about -fop-info:
>>
>>If OPTIONS is omitted, it defaults to 'all-all', which means
>> dump all available optimization info from all the passes.
>>
Hi,
as PR71214 points out gcc uses a wrong feature test macro for C++11
rvalue references: __cpp_rvalue_reference instead of the correct
__cpp_rvalue_references.
The fix is trivial. Ok for trunk and active branches?
Thanks.
c-family/ChangeLog
* c-cppbuiltin.c (c_cpp_builtins): Use __
On Mon, 4 Jul 2016, Martin Sebor wrote:
> On 07/04/2016 04:59 AM, Richard Biener wrote:
> > On Fri, 1 Jul 2016, Martin Sebor wrote:
> >
> > > The attached patch enhances compile-time checking for buffer overflow
> > > and output truncation in non-trivial calls to the sprintf family of
> > > funct
On Tue, 5 Jul 2016, Kyrill Tkachov wrote:
>
> On 01/07/16 13:02, Richard Biener wrote:
> > On Thu, 30 Jun 2016, Kyrill Tkachov wrote:
> >
> > > On 28/06/16 08:54, Richard Biener wrote:
> > > > On Thu, 16 Jun 2016, Kyrill Tkachov wrote:
> > > >
> > > > > On 15/06/16 22:53, Marc Glisse wrote:
> >
On Tue, 5 Jul 2016, Kyrill Tkachov wrote:
As for testing I've bootstrapped and tested the patch on aarch64 and
x86_64 with synth_shift_p in vect_synth_mult_by_constant hacked to be
always true to exercise the paths that synthesize the shift by
additions. Marc, could you test this on the sparc
This avoids doing useless work at the local level in gnat_to_gnu_entity.
Tested on x86_64-suse-linux, applied on the mainline.
2016-07-05 Eric Botcazou
* gcc-interface/decl.c (gnat_to_gnu_entity): Invoke global_bindings_p
last when possible. Do not call elaborate_expression_
On Tue, Jul 5, 2016 at 12:07 PM, Markus Trippelsdorf
wrote:
> Hi,
>
> as PR71214 points out gcc uses a wrong feature test macro for C++11
> rvalue references: __cpp_rvalue_reference instead of the correct
> __cpp_rvalue_references.
>
> The fix is trivial. Ok for trunk and active branches?
I wonde
On Fri, Jul 1, 2016 at 3:10 PM, Manish Goregaokar wrote:
> Added a test:
Ok if this passed bootstrap/regtest.
Richard.
> gcc/ChangeLog:
> PR c/71699
> * fold-const.c (tree_binary_nonzero_warnv_p): Allow
> pointer addition to also be considered nonzero.
>
> gcc/testsuite/ChangeLog:
>
Hi,
the deficiency comes from a chicken-and-egg problem during WPA: DECL nodes
merging depends on type merging, but type merging also depends on DECL nodes
merging for dynamic types declared at file scope, which easily occurs in Ada.
For the attached trivial testcase, the compiler issues:
/hom
Marc Glisse writes:
> On Tue, 5 Jul 2016, Kyrill Tkachov wrote:
>
>> As for testing I've bootstrapped and tested the patch on aarch64 and
>> x86_64 with synth_shift_p in vect_synth_mult_by_constant hacked to be
>> always true to exercise the paths that synthesize the shift by
>> additions. Marc,
On Fri, Jul 01, 2016 at 08:04:46PM -0500, Bill Schmidt wrote:
> Bootstrapped and tested on powerpc64le-unknown-linux-gnu with no regressions.
> Is this ok for trunk, and eventual 6.2 backport?
Okay for both. Just a few cosmetics:
> + /* If this is a VSX register, generate the special mfvsrd
On 05/07/16 12:24, Rainer Orth wrote:
Marc Glisse writes:
On Tue, 5 Jul 2016, Kyrill Tkachov wrote:
As for testing I've bootstrapped and tested the patch on aarch64 and
x86_64 with synth_shift_p in vect_synth_mult_by_constant hacked to be
always true to exercise the paths that synthesize th
On Tue, Jul 5, 2016 at 12:57 PM, Eric Botcazou wrote:
> Hi,
>
> the deficiency comes from a chicken-and-egg problem during WPA: DECL nodes
> merging depends on type merging, but type merging also depends on DECL nodes
> merging for dynamic types declared at file scope, which easily occurs in Ada.
Hi Bernd,
On 04/07/16 19:02, Bernd Schmidt wrote:
On 07/01/2016 11:18 AM, Kyrill Tkachov wrote:
In this arm wrong-code PR the struct assignment goes wrong when
expanding constructor elements to a register destination
when the constructor elements are signed bitfields less than a word wide.
In t
The loop combining partitions because of cost modeling is too optimistic
in skipping partition pairs to check. The hoisting patch exposes this,
the following fixes it.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2016-07-05 Richard Biener
* tree-loop-distr
The following patch fixes a FAIL of gcc.dg/tree-ssa/split-path-5.c
with hoisting enabled which leaves both cases of the testcase as
if (pred)
tmp = tmp + 4;
and thus with empty else (by hoisting a conversion). While this
eventually is if-convertible it shouldn't prevent path splitting
as th
On 04/07/16 12:19, Bernd Schmidt wrote:
On 07/04/2016 01:18 PM, Kyrill Tkachov wrote:
That does seem like it could cause trouble but I couldn't think of how
that sequence could appear or what its
semantics would be. Would assigning to the SImode reg 0 in your example
not touch the upper bits of
On Sun, 3 Jul 2016, Jan Hubicka wrote:
> Hi,
> this is updated version of patch. I finally convinced myself to read bit of
> wide-int.h and learnt some new things, like that they exists in multiple
> precisions. I always tought of wide-int as wider version of HOST_WIDE_INT
> that
> can hold all
On Tue, 5 Jul 2016, Richard Biener wrote:
given widest_int has only precision of TImode on x86_64?
Is that the case? The comments say:
It is really finite precision math where the precision is 4 times the
size of the largest integer that the target port can represent.
And the targe
>
> This can overflow for __uint128_t IV iterating to UINT128_MAX I think
> given widest_int has only precision of TImode on x86_64? An
> after-the-fact check like
>
>if (nit == 0)
> return true;
>
> does the trick I guess.
OK, I suppose we need to review niter and related code for s
> On Tue, 5 Jul 2016, Richard Biener wrote:
>
> >given widest_int has only precision of TImode on x86_64?
>
> Is that the case? The comments say:
>
> It is really finite precision math where the precision is 4 times the
> size of the largest integer that the target port can represent.
Hi All,
Here is a simple fix to cure regressions introduced by my fix for
70729. Patch also contains minor changes in test found by Jakub.
Bootstrapping and regression testing did not show any new failures.
Is it OK for trunk?
ChangeLog:
2016-07-05 Yuri Rumyantsev
PR tree-optimization/71734
This patch improves the accuracy of the Cortex-A53 integer scheduler,
resulting in performance gains across a wide range of benchmarks.
OK for commit?
ChangeLog:
2016-07-05 Wilco Dijkstra
* config/arm/cortex-a53.md: Use final_presence_set for in-order.
(cortex_a53_shift): Add
Thanks, committed as rev. 238007.
2016-07-04 14:41 GMT-06:00 Mikael Morin :
> Le 30/06/2016 06:05, Alessandro Fanfarillo a écrit :
>>
>> Dear Mikael,
>>
>> thanks for your review and for the test. The attached patch, built and
>> regtested for x86_64-pc-linux-gnu, addresses all the suggestions.
>>
On 07/05/2016 03:50 PM, Kyrill Tkachov wrote:
Ok, here's the updated patch with the assert replaced by failing the
conversion.
Bootstrapped and tested on x86_64. Also tested on aarch64.
Is this ok?
Sure. Thanks!
Bernd
Hi,
This patch adds several tests to check tails vectorization functionality.
Thanks,
Ilya
--
gcc/testsuite/
2016-07-05 Ilya Enkovich
* lib/target-supports.exp (check_avx2_hw_available): New.
(check_effective_target_avx2_runtime): New.
* gcc.dg/vect/vect-tail-combine-
On 04/07/16 20:44, Vladimir Makarov wrote:
On 06/30/2016 01:22 PM, Jiong Wang wrote:
Here is the patch,
From my understanding, "offmemok" is used to represent a memory operand
who's address we want to reload, and searching of it's reference location
seems confirmed my understanding as it's alw
On Tue, Jul 5, 2016 at 6:44 AM, Richard Biener
wrote:
> On Tue, Jul 5, 2016 at 12:07 PM, Markus Trippelsdorf
> wrote:
>> Hi,
>>
>> as PR71214 points out gcc uses a wrong feature test macro for C++11
>> rvalue references: __cpp_rvalue_reference instead of the correct
>> __cpp_rvalue_references.
>>
Senthil Kumar Selvaraj schrieb:
Senthil Kumar Selvaraj writes:
Hi,
This patch fixes a problem with fmerge-all-constants and the progmem
attribute - on trunk, the below testcase errors out with a section
conflict error.
When avr_asm_select_section renames .rodata.xyz section to
.prog
On 2016.07.05 at 12:21 -0400, Jason Merrill wrote:
> On Tue, Jul 5, 2016 at 6:44 AM, Richard Biener
> wrote:
> > On Tue, Jul 5, 2016 at 12:07 PM, Markus Trippelsdorf
> > wrote:
> >> Hi,
> >>
> >> as PR71214 points out gcc uses a wrong feature test macro for C++11
> >> rvalue references: __cpp_rva
On Tue, Jul 5, 2016 at 12:30 PM, Markus Trippelsdorf
wrote:
> On 2016.07.05 at 12:21 -0400, Jason Merrill wrote:
>> On Tue, Jul 5, 2016 at 6:44 AM, Richard Biener
>> wrote:
>> > On Tue, Jul 5, 2016 at 12:07 PM, Markus Trippelsdorf
>> > wrote:
>> >> Hi,
>> >>
>> >> as PR71214 points out gcc uses
Tested on Linux-X64.
2016-07-05 Ville Voutilainen
Implement LWG 2509,
any_cast doesn't work with rvalue reference targets and cannot
move with a value target.
* include/experimental/any (any(_ValueType&&)): Constrain and
add an overload that doesn't forward.
* include/e
On 05/07/16 20:33 +0300, Ville Voutilainen wrote:
Implement LWG 2509,
any_cast doesn't work with rvalue reference targets and cannot
move with a value target.
* include/experimental/any (any(_ValueType&&)): Constrain and
add an overload that doesn't forward.
* include/experiment
On Jul 5, 2016, at 1:39 AM, Kito Cheng wrote:
>
> pr69102.c use -fPIC flag in dg-options but not check is available for
> target, so I add "dg-require-effective-target fpic" for it.'
I happened to notice you didn't ask Ok?, and you didn't apply it or have it
applied. I'd recommend one or the o
Hi,
this patch makes ivopts to use iv_can_overflow_p on its candidates. This helps
to determine if candidate wraps in case it is not directly originating from IV
variable (i.e. it is derived IV or artificial one). For those we can not use
type information because we do now know if they are going to
Richard Biener writes:
> On Sun, 3 Jul 2016, Richard Sandiford wrote:
>
>> Richard Biener writes:
>> > On Wed, 15 Jun 2016, Richard Sandiford wrote:
>> >
>> >> Richard Biener writes:
>> >> > With the proposed cost change for vector construction we will end up
>> >> > vectorizing the testcase in
Tested on Linux-x64.
2016-07-05 Ville Voutilainen
Implement LWG 2451, optional should 'forward' T's
implicit conversions.
* include/experimental/optional (__is_optional_impl, __is_optional):
New.
(optional()): Make constexpr and default.
(optional(_Up&&), optional(const
Ping!
https://gcc.gnu.org/ml/gcc-patches/2016-05/msg01578.html
On 05/19/2016 11:42 PM, Jasmin J. wrote:
Hi!
Ping!
Attached is a rebased version of my patch due to commit
33ac16c8cc870229a6a08cd7037275b01e7a0b9d
*** gcc/ChangeLog ***
2016-04-19 Thomas Preud'homme
Jasmin Je
Hi Mike:
thanks for your review :)
On Wed, Jul 6, 2016 at 2:54 AM, Mike Stump wrote:
> On Jul 5, 2016, at 1:39 AM, Kito Cheng wrote:
>>
>> pr69102.c use -fPIC flag in dg-options but not check is available for
>> target, so I add "dg-require-effective-target fpic" for it.'
>
> I happened to noti
The following patch fixes a bug where we do not disable POWER9 vector dform
addressing when we compile for POWER9 but without VSX support. This manifested
itself with us trying to use dform addressing with altivec loads/stores
which is illegal, leading to an ICE.
This has bootstrapped and regtest
46 matches
Mail list logo
