On Fri, Sep 15, 2017 at 5:03 AM, Rainer Orth
wrote:
>
the patch broke Solaris bootstrap:
/vol/gcc/src/hg/trunk/local/libgo/go/syscall/exec_unix.go:240:11: error:
reference to undefined name 'forkExecPipe'
if err = forkExecPipe(p[:]); err != nil {
^
On 09/14/2017 06:17 AM, Martin Liška wrote:
> Hello.
>
> As mentioned at Cauldron 2017, second step in switch lowering should be
> massive
> simplification in code that does expansion of balanced tree. Basically it
> includes
> VRP and DCE, which we can for obvious reason do by our own.
>
> The
Hi!
I've backported 13 commits of mine and one from Richard.
Bootstrapped/regtested on x86_64-linux and i686-linux, committed
to gcc-6-branch.
Jakub
2017-09-15 Jakub Jelinek
Backported from mainline
2017-06-30 Jakub Jelinek
PR target/81225
* config/
The hash_map interface is a lot more convenient than that of
hash_table for cases where it makes sense, but there hasn't been a way
to get the ggc_cache_remove behavior with a hash_map. In other words,
not marking elements during the initial ggc marking phase, but maybe
marking them during the cle
On Fri, Sep 15, 2017 at 10:06:40AM -0500, Will Schmidt wrote:
> This is a test created during investigation of the feedback on
> the rs6000 gimple vector folding code, regarding the handling of
> arg1_type. Inspired by feedback from Richard and Bill.
>
> This was useful to illustrate the issue
This patch by Cherry Zhang changes the Go frontend to call
error_statement when generating GIMPLE for a fallthrough in the last
case in a switch. This avoids generating incorrect IR in an erroneous
case. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu.
Committed to mainline.
Ian
Index:
Hi Will,
On Fri, Sep 15, 2017 at 09:59:54AM -0500, Will Schmidt wrote:
> +/* Vector loads. */
> +case ALTIVEC_BUILTIN_LVX_V16QI:
> +case ALTIVEC_BUILTIN_LVX_V8HI:
> +case ALTIVEC_BUILTIN_LVX_V4SI:
> +case ALTIVEC_BUILTIN_LVX_V4SF:
> +case ALTIVEC_BUILTIN_LVX_V2DI:
> +c
This patch by Cherry Zhang to the Go frontend checks for an error
expression in Array_type::get_backend_length. Otherwise, a zero
length is created in the backend and the backend doesn't know there is
an error. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu.
Committed to mainline.
Ian
On Power8 little endian, two instructions are needed to load from the
natural in-memory representation of a vector into a vector register: a
load followed by a swap. When the vector value to be loaded is a
constant, more efficient code can be achieved by swapping the
representation of the constan
C11 semantics for excess precision (from N1531) are that an implicit
conversion (from the usual arithmetic conversions, not by assignment)
from integer to floating point has a result in the corresponding
evaluation format of that floating-point type, so possibly with excess
precision (whereas a cas
PR 81356 points out that doing a __builtin_strcpy of an empty string on
aarch64 does a copy from memory instead of just writing out a zero byte.
In looking at this I found that it was because of
aarch64_use_by_pieces_infrastructure_p, which returns false for
STORE_BY_PIECES. The comment says:
/
On Fri, 15 Sep 2017, Nathan Sidwell wrote:
> On 09/12/2017 12:48 PM, Joseph Myers wrote:
>
> > I'd be concerned about the possibility of a qsort implementation that
> > calls the comparison function with two pointers to the same object (as far
> > as I can tell, it's valid for qsort to do that).
OK.
On Fri, Sep 15, 2017 at 8:49 AM, Jakub Jelinek wrote:
> Hi!
>
> On Thu, Sep 14, 2017 at 11:28:09PM +0200, Jakub Jelinek wrote:
>> > I'd be tempted to say leave all this, and march 1z -> 2a for the _next_
>> > standard. 2020 or so is a good first stab at the date.
>>
>> I didn't want to add
On 09/12/2017 12:48 PM, Joseph Myers wrote:
I'd be concerned about the possibility of a qsort implementation that
calls the comparison function with two pointers to the same object (as far
as I can tell, it's valid for qsort to do that). That is, I think you
need to check for the two DECLs bein
Hello,
I'd like to apply the following LRA patch to make qsort comparator
reload_pseudo_compare_func proper (right now it lacks transitivity
due to incorrect use of non_reload_pseudos bitmap, PR 68988).
This function was originally a proper comparator, and the problematic
code was added as a fix
As I mentioned a few months back, I intended to step down as a vxworks
maintainer. Olivier is more than capable of looking after the target,
plus he has hardware.
I've committed this patch.
nathan
--
Nathan Sidwell
2017-09-15 Nathan Sidwell
* MAINTAINERS: Remove myself as a vxworks maint
On 09/15/2017 11:07 AM, Nathan Sidwell wrote:
On 09/14/2017 04:26 PM, Jakub Jelinek wrote:
There is one 1z spot in gcc/doc/standards.texi, but that whole paragraph
looks wrong, can somebody please rewrite it to match the reality?
This patch addresses that paragraph. I've rewritten it using t
On 09/14/2017 04:26 PM, Jakub Jelinek wrote:
There is one 1z spot in gcc/doc/standards.texi, but that whole paragraph
looks wrong, can somebody please rewrite it to match the reality?
This patch addresses that paragraph. I've rewritten it using the c++11
and C++14 examples and removed any re
On 15/09/17 16:38, Charles Baylis wrote:
On 13 September 2017 at 10:02, Kyrill Tkachov
wrote:
Hi Charles,
On 12/09/17 09:34, charles.bay...@linaro.org wrote:
From: Charles Baylis
This patch moves the calculation of costs for MEM into a
separate function, and reforms the calculation into t
On 15/09/17 16:38, Charles Baylis wrote:
On 13 September 2017 at 10:02, Kyrill Tkachov
wrote:
Hi Charles,
On 12/09/17 09:34, charles.bay...@linaro.org wrote:
From: Charles Baylis
Add bus widths. These use the approximation that v7 and later cores have
64bit data bus width, and earlier cor
On 09/13/2017 12:00 PM, Steve Ellcey wrote:
> This patch fixes the documentation issues pointed out in PR target/82066.
> It may be considered obvious enough to just check in but I'd rather have
> someone look it over to make sure I didn't mess something up.
>
> Steve Ellcey
> sell...@cavium.com
>
On 15/09/17 16:38, Charles Baylis wrote:
On 13 September 2017 at 10:02, Kyrill Tkachov
wrote:
Please add a comment here saying that the units are in COSTS_N_INSNS
so that we can reduce the temptation to use these in inappropriate contexts.
+ if (VECTOR_MODE_P (mode))
+ {
+
On 09/15/2017 05:15 PM, Pedro Alves wrote:
> On 09/15/2017 01:04 PM, Nathan Sidwell wrote:
>>
>>
>> Pedro, would you like me to port to gdb's libiberty, or will you do a
>> merge in the near future?
>
> I wasn't planning to, but I'm doing it now.
>
Now done:
https://sourceware.org/ml/gdb-patche
On 09/13/2017 03:20 PM, Wilco Dijkstra wrote:
> Jeff Law wrote:
>> On 09/06/2017 03:55 AM, Jackson Woodruff wrote:
>>> On 08/30/2017 01:46 PM, Richard Biener wrote:
>
rdivtmp = 1 / (y*C);
tem = x *rdivtmp;
tem2= z * rdivtmp;
instead of
rdivtmp = 1/y;
On Fri, 15 Sep 2017, Wilco Dijkstra wrote:
Marc Glisse wrote:
The question is whether, having computed c=a/b, it is cheaper to test a
No, a
This would indicate that we do not need to check for single-use, makes the
patch simpler, thanks.
(let's ignore -Os)
--
Marc Glisse
On 09/15/2017 06:10 PM, Jeff Law wrote:
OK.
jeff
Committed. Thanks!
--
Pierre-Marie de Rodat
On 09/15/2017 01:04 PM, Nathan Sidwell wrote:
>
>
> Pedro, would you like me to port to gdb's libiberty, or will you do a
> merge in the near future?
I wasn't planning to, but I'm doing it now.
Thanks much for the fix!
--
Pedro Alves
Marc Glisse wrote:
> The question is whether, having computed c=a/b, it is cheaper to test a c!=0.
> I think it is usually the second one, but not for all types on all targets.
> Although since
> you mention VRP, it is easier to do further optimizations using the
> information a
On 09/15/2017 05:07 AM, Eric Botcazou wrote:
> Hi,
>
> this plugs the hole reported by Florian on the gcc@ list, namely that no
> warning is issued with -Wall in C++ on pragma scalar_storage_order.
>
> Tested on x86_64-suse-linux, OK for the mainline? And some branches?
>
>
> 2017-09-15 Eric
On 09/15/2017 08:48 AM, Pierre-Marie de Rodat wrote:
> On 09/15/2017 12:54 PM, Pierre-Marie de Rodat wrote:
>> I’m not super confident about this though, so I’ll resubmit a patch
>> without the reordering: I’ve added more comments anyway as I’ve
>> learned more about this since yesterday. ;-)
>
>
On 09/15/2017 09:55 AM, Marc Glisse wrote:
> On Fri, 15 Sep 2017, Jeff Law wrote:
>
>> On 09/15/2017 07:09 AM, Marc Glisse wrote:
>>> On Fri, 15 Sep 2017, Prathamesh Kulkarni wrote:
>>>
>>> +/* (X / Y) == 0 -> X < Y if X, Y are unsigned. */
>>> +(simplify
>>> + (eq (trunc_div @0 @1) integer_zero
On 09/14/2017 04:26 PM, Jakub Jelinek wrote:
Hi!
Given https://herbsutter.com/2017/09/06/c17-is-formally-approved/
this patch makes -std=c++17 and -std=gnu++17 the documented options
and -std=c++1z and -std=gnu++1z deprecated aliases, adjusts diagnostics etc.
Bootstrapped/regtest on x86_64-linu
Hi!
When we have (x >> y) & 0x1fff or similar (for non-constant y or
even for constant y if y + 13 is bigger than x's bits) and x is
a non-paradoxical lowpart subreg (in the testcase (subreg:SI (reg:DI ...) 0))
then the lshiftrt extracts some bits out (0 to 13) out of the wider
DImode registers st
On 09/15/2017 05:53 AM, Paolo Carlini wrote:
Hi,
gently pinging this.
On 16/06/2017 15:47, Paolo Carlini wrote:
Hi,
submitter and Manuel analyzed this a while ago and came to the
conclusion - which I think is still valid vs the current working draft
- that strictly speaking this kind of cod
On Fri, 15 Sep 2017, Jeff Law wrote:
On 09/15/2017 07:09 AM, Marc Glisse wrote:
On Fri, 15 Sep 2017, Prathamesh Kulkarni wrote:
+/* (X / Y) == 0 -> X < Y if X, Y are unsigned. */
+(simplify
+ (eq (trunc_div @0 @1) integer_zerop)
+ (if (TYPE_UNSIGNED (TREE_TYPE(@0)) && TYPE_UNSIGNED (TREE_TY
On 09/15/2017 04:49 AM, Richard Sandiford wrote:
> The vectoriser was calling vect_get_smallest_scalar_type without
> having proven that the type actually is a scalar. This seems to
> be the intended behaviour: the ultimate test of whether the type
> is interesting (and hence scalar) is whether an
On Thu, 14 Sep 2017, Bernd Edlinger wrote:
> Hi,
>
> as suggested by Joseph, here is an updated patch that
> uses min_align_of_type instead of TYPE_ALIGN.
>
> Is it OK?
OK.
--
Joseph S. Myers
jos...@codesourcery.com
On 09/15/2017 04:47 AM, Richard Sandiford wrote:
> vectorizable_mask_load_store was not passing the required mask type to
> vect_get_vec_def_for_operand. This doesn't matter for masks that are
> defined in the loop, since their STMT_VINFO_VECTYPE will be what we need
> anyway. But it's not possib
On Sat, Sep 9, 2017 at 1:27 PM, Ian Lance Taylor wrote:
>
> The patch to include/ansidecl.h is basically OK. Please add an
> example in the comment showing how to use it: after `private:`, and
> with a trailing semicolon. Thanks.
Patch below is committed. Thanks for the review.
>
> The patche
Hi Carl,
On Thu, Sep 14, 2017 at 02:23:47PM -0700, Carl Love wrote:
> vecload isn't really the correct type for this, but I see we have the
> same on the existing lvsl patterns (it's permute unit on p9; I expect
> the same on p8 and older, but please check).
It is a bit more complicated on older
On 09/15/2017 04:48 AM, Richard Sandiford wrote:
> Without this we'd pick an unrolling factor based purely on longs,
> ignoring the ints. It's posssible that vect_get_smallest_scalar_type
> should also handle shifts, but I think we'd still want this as a
> belt-and-braces fix.
>
> Tested on aarch
On 09/15/2017 04:45 AM, Richard Sandiford wrote:
> This patch changes the type of the multiplier applied by
> vectorizable_live_operation from unsigned_type_node to bitsizetype,
> which matches the type of TYPE_SIZE and is the type expected of a
> BIT_FIELD_REF bit position. This is shown by exist
On 04/09/17 03:31 -0700, Tim Shen via libstdc++ wrote:
This fixes the follow-up comments in 71500.
Back-reference matching is different from other matching, as the
content the back-reference refers to is at "run-time", aka during
regex_match(), not regex() compilation.
For compilation we do hav
On 09/15/2017 04:45 AM, Richard Sandiford wrote:
> vectorizable_live_operation needs to use BIT_FIELD_REF to extract one
> element of a vector. For a packed vector boolean type, the number of
> bits to extract should be taken from TYPE_PRECISION rather than TYPE_SIZE.
>
> This is shown by existin
On 13 September 2017 at 10:02, Kyrill Tkachov
wrote:
> Hi Charles,
>
> On 12/09/17 09:34, charles.bay...@linaro.org wrote:
>>
>> From: Charles Baylis
>>
>> This patch moves the calculation of costs for MEM into a
>> separate function, and reforms the calculation into two
>> parts. Firstly any ad
On 13 September 2017 at 10:02, Kyrill Tkachov
wrote:
>
> Please add a comment here saying that the units are in COSTS_N_INSNS
> so that we can reduce the temptation to use these in inappropriate contexts.
>> + if (VECTOR_MODE_P (mode))
>> + {
>> + *cost += current_tune->addr_
On 13 September 2017 at 10:02, Kyrill Tkachov
wrote:
> Hi Charles,
>
> On 12/09/17 09:34, charles.bay...@linaro.org wrote:
>>
>> From: Charles Baylis
>>
>> Add bus widths. These use the approximation that v7 and later cores have
>> 64bit data bus width, and earlier cores have 32 bit bus width, w
On 13 September 2017 at 10:02, Kyrill Tkachov
wrote:
>
> Please add a comment here saying that the units are in COSTS_N_INSNS
> so that we can reduce the temptation to use these in inappropriate contexts.
>> + if (VECTOR_MODE_P (mode))
>> + {
>> + *cost += current_tune->addr_
On 09/15/2017 04:44 AM, Richard Sandiford wrote:
> vect_transform_stmt calls vectorizable_live_operation for
> each live statement in an SLP node, but vect_analyze_stmt
> only called it the once. This patch makes vect_analyze_stmt
> consistent with vect_transform_stmt, which should be a bit
> more
> -Original Message-
> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-
> ow...@gcc.gnu.org] On Behalf Of Jeff Law
> Sent: Friday, August 25, 2017 11:03 PM
> To: Tsimbalist, Igor V ; 'gcc-
> patc...@gcc.gnu.org'
> Subject: Re: 0006-Part-6.-Add-x86-tests-for-Intel-CET-implementation
On 09/15/2017 04:43 AM, Richard Sandiford wrote:
> Previously SLP_TREE_NUMBER_OF_VEC_STMTS was calculated while scheduling
> an SLP tree after analysis, but sometimes it can be useful to know the
> value during analysis too. This patch moves the calculation to
> vect_slp_analyze_node_operaions ins
On 09/15/2017 03:42 AM, Richard Biener wrote:
> On Fri, Sep 15, 2017 at 5:44 AM, Andrew Pinski wrote:
>> On Thu, Sep 14, 2017 at 6:30 PM, Kugan Vivekanandarajah
>> wrote:
>>> This patch prevent tree unroller from completely unrolling inner loops if
>>> that
>>> results in excessive strided-loads
> -Original Message-
> From: Jeff Law [mailto:l...@redhat.com]
> Sent: Friday, August 25, 2017 10:59 PM
> To: Tsimbalist, Igor V ; 'gcc-
> patc...@gcc.gnu.org'
> Subject: Re: 0002-Part-2.-Document-finstrument-control-flow-and-notrack
> attribute
>
> On 08/01/2017 02:56 AM, Tsimbalist, Igo
On 09/15/2017 07:09 AM, Marc Glisse wrote:
> On Fri, 15 Sep 2017, Prathamesh Kulkarni wrote:
>
> +/* (X / Y) == 0 -> X < Y if X, Y are unsigned. */
> +(simplify
> + (eq (trunc_div @0 @1) integer_zerop)
> + (if (TYPE_UNSIGNED (TREE_TYPE(@0)) && TYPE_UNSIGNED (TREE_TYPE (@1)))
> +(lt @0 @1)))
Hi,
This is a test created during investigation of the feedback on
the rs6000 gimple vector folding code, regarding the handling of
arg1_type. Inspired by feedback from Richard and Bill.
This was useful to illustrate the issue to me. Whether this is a
valid test for the testsuite I'll defer t
Hi guys,
I was looking at merging libiberty&include from gcc to binutils-gdb,
and noticed this one patch that is in binutils-gdb and not in gcc,
since last July.
I think the patch is borderline obvious (it's arguable whether
to define OVERRIDE/FINAL for C), but in interest of re-syncing
the trees
Hi,
[PATCH, rs6000] [v3] Folding of vector loads in GIMPLE
Folding of vector loads in GIMPLE.
Add code to handle gimple folding for the vec_ld builtins.
Remove the now obsoleted folding code for vec_ld from rs6000-c.c. Surrounding
comments have been adjusted slightly so they continue to
On 09/15/2017 12:54 PM, Pierre-Marie de Rodat wrote:
I’m not super confident about this though, so I’ll resubmit a patch
without the reordering: I’ve added more comments anyway as I’ve learned
more about this since yesterday. ;-)
Here it is!
--
Pierre-Marie de Rodat
>From 601dd0e949f4af456a11
One more also for GCC 5 branch.
Martin
>From 6853238cc8103fefb8b8acc8f56d444860495714 Mon Sep 17 00:00:00 2001
From: marxin
Date: Fri, 11 Aug 2017 10:01:13 +
Subject: [PATCH] Backport r251049
gcc/ChangeLog:
2017-08-11 Martin Liska
PR tree-opt/79987
* tree-chkp.c (chkp_get_bounds_for_d
One more.
Martin
>From 6853238cc8103fefb8b8acc8f56d444860495714 Mon Sep 17 00:00:00 2001
From: marxin
Date: Fri, 11 Aug 2017 10:01:13 +
Subject: [PATCH] Backport r251049
gcc/ChangeLog:
2017-08-11 Martin Liska
PR tree-opt/79987
* tree-chkp.c (chkp_get_bounds_for_decl_addr): Do not inst
On Sep 15, 2017, at 4:13 AM, Richard Biener wrote:
>
> On Thu, Sep 14, 2017 at 4:38 PM, Bill Schmidt
> wrote:
>> On Sep 14, 2017, at 5:15 AM, Richard Biener
>> wrote:
>>>
>>> On Wed, Sep 13, 2017 at 10:14 PM, Bill Schmidt
>>> wrote:
On Sep 13, 2017, at 10:40 AM, Bill Schmidt
wrot
On 13 September 2017 at 18:33, Kyrill Tkachov
wrote:
> Hi Christophe,
>
>
> On 13/09/17 16:23, Christophe Lyon wrote:
>>
>> Hi,
>>
>> On 12 October 2016 at 11:22, Christophe Lyon
>> wrote:
>>>
>>> On 12 October 2016 at 11:14, Kyrill Tkachov
>>> wrote:
On 12/10/16 09:59, Christophe Lyo
On Fri, 15 Sep 2017, Prathamesh Kulkarni wrote:
+/* (X / Y) == 0 -> X < Y if X, Y are unsigned. */
+(simplify
+ (eq (trunc_div @0 @1) integer_zerop)
+ (if (TYPE_UNSIGNED (TREE_TYPE(@0)) && TYPE_UNSIGNED (TREE_TYPE (@1)))
+(lt @0 @1)))
+
+/* (X / Y) != 0 -> X >= Y, if X, Y are unsigned. */
On Fri, Sep 15, 2017 at 12:49 PM, Richard Biener
wrote:
> On Thu, Sep 14, 2017 at 5:02 PM, Bin Cheng wrote:
>> Hi,
>> Current pcom implementation rewrites into lcssa form after all loops are
>> transformed, this is
>> not enough because unrolling of later loop checks lcssa form in function
>> t
On 09/15/2017 01:53 PM, Jakub Jelinek wrote:
> On Mon, Aug 07, 2017 at 02:17:17PM +0100, Pedro Alves wrote:
>> I happened to skim this patch and notice a couple issues.
>> See below.
>
> Note I've just posted updated patch based on this to gcc-patches.
Thanks ( FWIW :-) ).
>>> @@ -497,7 +499,10
On Mon, Aug 07, 2017 at 02:17:17PM +0100, Pedro Alves wrote:
> I happened to skim this patch and notice a couple issues.
> See below.
Note I've just posted updated patch based on this to gcc-patches.
> > +/* Set the C++ 202a draft standard (without GNU extensions if ISO). */
> > +static void
> >
Hi!
On Thu, Sep 14, 2017 at 11:28:09PM +0200, Jakub Jelinek wrote:
> > I'd be tempted to say leave all this, and march 1z -> 2a for the _next_
> > standard. 2020 or so is a good first stab at the date.
>
> I didn't want to add c++2a and gnu++2a in the same patch, it can be added
> incrementally
On 1 September 2017 at 08:09, Prathamesh Kulkarni
wrote:
> On 17 August 2017 at 18:02, Prathamesh Kulkarni
> wrote:
>> On 8 August 2017 at 09:50, Prathamesh Kulkarni
>> wrote:
>>> On 31 July 2017 at 23:53, Prathamesh Kulkarni
>>> wrote:
On 23 May 2017 at 19:10, Prathamesh Kulkarni
wr
One more that I've just tested.
Martin
>From 69bdfd4b8d845d2262139b4406cfd9f2d947f80d Mon Sep 17 00:00:00 2001
From: marxin
Date: Wed, 28 Jun 2017 07:59:23 +
Subject: [PATCH] Backport r249728
gcc/ChangeLog:
2017-06-28 Martin Liska
PR sanitizer/81224
* asan.c (instrument_derefs): Bail
On Fri, Sep 15, 2017 at 1:12 PM, Tsimbalist, Igor V
wrote:
>> -Original Message-
>> From: Tsimbalist, Igor V
>> Sent: Tuesday, September 12, 2017 5:35 PM
>> To: 'Richard Biener'
>> Cc: 'gcc-patches@gcc.gnu.org' ; Tsimbalist, Igor V
>>
>> Subject: RE: 0001-Part-1.-Add-generic-part-for-Int
Hello.
I'm going to install following backports.
Patches can bootstrap on ppc64le-redhat-linux and survives regression tests.
Martin
>From baece18f7986907d9cd7cedea78fea9b1d7ef895 Mon Sep 17 00:00:00 2001
From: marxin
Date: Wed, 28 Jun 2017 07:59:23 +
Subject: [PATCH 6/6] Backport r249728
This fixes simple_object_elf_copy_lto_debug_sections to properly
iterate the marking sections as necessary process.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2017-09-15 Richard Biener
PR lto/81968
* simple-object-elf.c (simple_object_elf_copy_lto
On Wed, Sep 13, 2017 at 11:20 PM, Wilco Dijkstra wrote:
> Jeff Law wrote:
>> On 09/06/2017 03:55 AM, Jackson Woodruff wrote:
>> > On 08/30/2017 01:46 PM, Richard Biener wrote:
>
rdivtmp = 1 / (y*C);
tem = x *rdivtmp;
tem2= z * rdivtmp;
instead of
rdivtmp
Hi.
In order to make the code simple and transparent, I suggest to revert r238089.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Ready to be installed?
Martin
>From 0a865d51a5f61d0fa13e5d4eea208c62ff89e32e Mon Sep 17 00:00:00 2001
From: marxin
Date: Fri, 15 Sep 2017
This patch fixes PR82195, which turned out to be a demangler bug -- the
specification and the compiler were DTRT.
The originating source contained a non-generic lambda within a generic
lambda. Because we had an older GDB without recursion protection in its
demangler, GDB died, and that kind o
Hi Ian,
>>> the patch broke Solaris bootstrap:
>>>
>>> /vol/gcc/src/hg/trunk/local/libgo/go/syscall/exec_unix.go:240:11: error:
>>> reference to undefined name 'forkExecPipe'
>>> if err = forkExecPipe(p[:]); err != nil {
>>>^
>>>
>>> libgo/go/syscall/forkpipe_bsd.go is needed on Sol
Jeff Law writes:
> On 09/13/2017 01:19 PM, Richard Sandiford wrote:
>> Tested on aarch64-linux-gnu, x86_64-linux-gnu and powerpc64le-linux-gnu.
>> Also tested by comparing the testsuite assembly output on at least one
>> target per CPU directory. OK to install?
>>
>> Richard
>>
>>
>> 2017-09-1
On Thu, Sep 14, 2017 at 5:02 PM, Bin Cheng wrote:
> Hi,
> Current pcom implementation rewrites into lcssa form after all loops are
> transformed, this is
> not enough because unrolling of later loop checks lcssa form in function
> tree_transform_and_unroll_loop.
> This simple patch rewrites loop
Hi!
I've bootstrapped/regtested (x86_64-linux and i686-linux) and committed
following
4 backports to gcc-7-branch:
Jakub
2017-09-15 Jakub Jelinek
Backported from mainline
2017-09-12 Jakub Jelinek
PR target/82112
* c-common.c (sync_resolve_size): In
> -Original Message-
> From: Tsimbalist, Igor V
> Sent: Tuesday, September 12, 2017 5:35 PM
> To: 'Richard Biener'
> Cc: 'gcc-patches@gcc.gnu.org' ; Tsimbalist, Igor V
>
> Subject: RE: 0001-Part-1.-Add-generic-part-for-Intel-CET-enabling
>
> > -Original Message-
> > From: Tsimbal
Hi,
this plugs the hole reported by Florian on the gcc@ list, namely that no
warning is issued with -Wall in C++ on pragma scalar_storage_order.
Tested on x86_64-suse-linux, OK for the mainline? And some branches?
2017-09-15 Eric Botcazou
* c-pragma.c (handle_pragma_scalar_storage
Hi,
This patch adds the transforms mentioned in $subject.
Bootstrap+test in progress on x86_64-unknown-linux-gnu.
OK to commit if passes ?
Thanks,
Prathamesh
2017-09-15 Prathamesh Kulkarni
* match.pd ((X / Y) == 0 -> X < Y): New pattern.
((X / Y) != 0 -> X >= Y): Likewise.
tes
On 09/14/2017 07:16 PM, Jeff Law wrote:
The comment additions are fine. What's the rationale behind the
ordering of the fields? In general we want the opposite order from what
you did -- going from most strictly aligned to least strictly aligned
minimizes the amount of unused padding.
Thank y
The vectoriser was calling vect_get_smallest_scalar_type without
having proven that the type actually is a scalar. This seems to
be the intended behaviour: the ultimate test of whether the type
is interesting (and hence scalar) is whether an associated vector
type exists, but this is only tested l
In working on bug 82195, a lambda-related demangler bug, I noticed some
cleanup opportunities.
1) we express an is_fnqual_component_type in two separate, independent,
ways. It would be smarter to express one of those ways in terms of the
other.
2) An overly nested function call made it awkw
In working on bug 82195, a lambda-related demangler bug, I noticed some
cleanup opportunities.
1) we express an is_fnqual_component_type in two separate, independent,
ways. It would be smarter to express one of those ways in terms of the
other.
2) An overly nested function call made it awkw
Without this we'd pick an unrolling factor based purely on longs,
ignoring the ints. It's posssible that vect_get_smallest_scalar_type
should also handle shifts, but I think we'd still want this as a
belt-and-braces fix.
Tested on aarch64-linux-gnu, x86_64-linux-gnu and powerpc64le-linux-gnu.
OK
vectorizable_mask_load_store was not passing the required mask type to
vect_get_vec_def_for_operand. This doesn't matter for masks that are
defined in the loop, since their STMT_VINFO_VECTYPE will be what we need
anyway. But it's not possible to tell which mask type the caller needs
when looking
vectorizable_live_operation needs to use BIT_FIELD_REF to extract one
element of a vector. For a packed vector boolean type, the number of
bits to extract should be taken from TYPE_PRECISION rather than TYPE_SIZE.
This is shown by existing tests once SVE is added.
Tested on aarch64-linux-gnu, x8
This patch changes the type of the multiplier applied by
vectorizable_live_operation from unsigned_type_node to bitsizetype,
which matches the type of TYPE_SIZE and is the type expected of a
BIT_FIELD_REF bit position. This is shown by existing tests when
SVE is added.
Tested on aarch64-linux-gnu
vect_transform_stmt calls vectorizable_live_operation for
each live statement in an SLP node, but vect_analyze_stmt
only called it the once. This patch makes vect_analyze_stmt
consistent with vect_transform_stmt, which should be a bit
more robust, and also means that a later patch can use
slp_inde
Previously SLP_TREE_NUMBER_OF_VEC_STMTS was calculated while scheduling
an SLP tree after analysis, but sometimes it can be useful to know the
value during analysis too. This patch moves the calculation to
vect_slp_analyze_node_operaions instead.
This became more natural after:
2017-06-30 Richa
On Fri, Sep 15, 2017 at 2:53 AM, Richard Biener wrote:
> On Thu, 14 Sep 2017, David Edelsohn wrote:
>
>> * tree-ssa-sccvn.c (visit_phi): Merge undefined values similar
>> to VN_TOP.
>>
>> This seems to have regressed
>>
>> FAIL: gcc.dg/tree-prof/time-profiler-2.c scan-ipa-dump-times profile
>> "Re
Hi,
gently pinging this.
On 16/06/2017 15:47, Paolo Carlini wrote:
Hi,
submitter and Manuel analyzed this a while ago and came to the
conclusion - which I think is still valid vs the current working draft
- that strictly speaking this kind of code violates [dcl.dcl], thus a
pedwarn seems mo
On Fri, Sep 15, 2017 at 5:44 AM, Andrew Pinski wrote:
> On Thu, Sep 14, 2017 at 6:30 PM, Kugan Vivekanandarajah
> wrote:
>> This patch prevent tree unroller from completely unrolling inner loops if
>> that
>> results in excessive strided-loads in outer loop.
>
> Same comments from the RTL versio
On Fri, Sep 15, 2017 at 3:31 AM, Kugan Vivekanandarajah
wrote:
> Change iv_analyze_result to take const_rtx. This is just to make the
> next patch compile. No functional changes:
Ok.
Richard.
> Thanks,
> Kugan
>
> gcc/ChangeLog:
>
> 2017-09-12 Kugan Vivekanandarajah
>
> * cfgloop.h (iv_a
On Fri, Sep 15, 2017 at 3:27 AM, Kugan Vivekanandarajah
wrote:
> This patch adds separate params for rtl unroller so that they can be
> tunned accordingly. Default values I have are based on some testing on
> aarch64. I am happy to leave it as the current value and set them in
> the back-end.
PAR
On 09/15/2017 10:26 AM, Martin Liška wrote:
> Hello.
>
> I'm going to install following backports.
>
> Patches can bootstrap on ppc64le-redhat-linux and survives regression tests.
>
> Martin
>
Small correction as gcc/c-family/c-attribs.c file was created in time of GCC 6.
Thus there's updated
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2017-09-15 Richard Biener
PR tree-optimization/82217
* tree-ssa-sccvn.c (visit_phi): Properly handle all VN_TOP
but not undefined case.
* gcc.dg/torture/pr82217.c: New testcase.
Index: gc
On Thu, Sep 14, 2017 at 4:38 PM, Bill Schmidt
wrote:
> On Sep 14, 2017, at 5:15 AM, Richard Biener
> wrote:
>>
>> On Wed, Sep 13, 2017 at 10:14 PM, Bill Schmidt
>> wrote:
>>> On Sep 13, 2017, at 10:40 AM, Bill Schmidt
>>> wrote:
On Sep 13, 2017, at 7:23 AM, Richard Biener
wro
1 - 100 of 107 matches
Mail list logo
