On Tue, 24 Jul 2018, Jeff Law wrote:
> On 07/24/2018 01:59 AM, Bernd Edlinger wrote:
> > Hi!
> >
> > This patch makes strlen range computations more conservative.
> >
> > Firstly if there is a visible type cast from type A to B before passing
> > then value to strlen, don't expect the type layou
On Tue, 24 Jul 2018, Bernd Edlinger wrote:
> On 07/24/18 23:46, Jeff Law wrote:
> > On 07/24/2018 01:59 AM, Bernd Edlinger wrote:
> >> Hi!
> >>
> >> This patch makes strlen range computations more conservative.
> >>
> >> Firstly if there is a visible type cast from type A to B before passing
> >>
On Tue, Jul 24, 2018 at 7:18 PM Segher Boessenkool
wrote:
>
> This patch allows combine to combine two insns into two. This helps
> in many cases, by reducing instruction path length, and also allowing
> further combinations to happen. PR85160 is a typical example of code
> that it can improve.
On Wed, Jul 25, 2018 at 4:07 AM Martin Sebor wrote:
>
> The very large option argument enhancement committed last week
> inadvertently introduced an assumption about the LP64 data model
> that makes the -Wxxx-larger-than options have a different effect
> at their default documented setting of PTRD
On Tue, Jul 24, 2018 at 11:53 AM Richard Sandiford
wrote:
>
> This minor clean-up avoids repeating the test for double reductions
> and also moves the vect_get_vec_def_for_operand call to the same
> function as the corresponding vect_get_vec_def_for_stmt_copy.
OK.
>
> 2018-07-24 Richard Sandifo
On Tue, Jul 24, 2018 at 11:53 AM Richard Sandiford
wrote:
>
> vectorizable_reduction has old code to cope with cases in which the
> given statement belongs to a reduction group but isn't the first statement.
> That can no longer happen, since all statements in the group go into the
> same SLP node
On Tue, Jul 24, 2018 at 11:53 AM Richard Sandiford
wrote:
>
> vect_free_slp_tree had:
>
> gimple *stmt;
> FOR_EACH_VEC_ELT (SLP_TREE_SCALAR_STMTS (node), i, stmt)
> /* After transform some stmts are removed and thus their vinfo is gone.
> */
> if (vinfo_for_stmt (stmt))
> {
>
On Tue, Jul 24, 2018 at 11:54 AM Richard Sandiford
wrote:
>
> vect_is_slp_reduction and vect_is_simple_reduction had two instances
> each of:
>
> && (is_gimple_assign (def_stmt)
> || is_gimple_call (def_stmt)
> || STMT_VINFO_DEF_TYPE (vinfo_for_stm
On Tue, Jul 24, 2018 at 11:54 AM Richard Sandiford
wrote:
>
> The usual vectoriser dance to create new assignments is:
>
> new_stmt = gimple_build_assign (vec_dest, ...);
> new_temp = make_ssa_name (vec_dest, new_stmt);
> gimple_assign_set_lhs (new_stmt, new_temp);
>
> but one site in
On Mon, Jul 23, 2018 at 5:05 PM Richard Sandiford
wrote:
>
> Marc Glisse writes:
> > On Fri, 20 Jul 2018, Richard Sandiford wrote:
> >
> >> --- gcc/match.pd 2018-07-18 18:44:22.565914281 +0100
> >> +++ gcc/match.pd 2018-07-20 11:24:33.692045585 +0100
> >> @@ -4924,3 +4924,37 @@ DEFINE_INT
On Tue, Jul 24, 2018 at 11:55 AM Richard Sandiford
wrote:
>
> This patch adds a vec_info function for allocating and setting
> stmt_vec_infos. It's the start of a long process of removing
> the global stmt_vec_info array.
>
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vectorizer.
On Tue, Jul 24, 2018 at 11:55 AM Richard Sandiford
wrote:
>
> This patch adds a vec_info replacement for vinfo_for_stmt. The main
> difference is that the new routine can cope with arbitrary statements,
> so there's no need to call vect_stmt_in_region_p first.
>
> The patch only converts calls th
On Tue, Jul 24, 2018 at 11:55 AM Richard Sandiford
wrote:
>
> This patch adds a vec_info helper for checking whether an operand is an
> SSA_NAME that is defined in the vectorisable region.
OK.
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vectorizer.h (vec_info::lookup_def): Decl
On Tue, Jul 24, 2018 at 11:56 AM Richard Sandiford
wrote:
>
> This patch adds a helper function for seeing whether there is a single
> user of an SSA name, and whether that user has a stmt_vec_info.
OK.
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vectorizer.h (vec_info::lookup_
On Tue, Jul 24, 2018 at 11:57 AM Richard Sandiford
wrote:
>
> This patch turns stmt_vec_info into an unspeakably bad wrapper class
> and adds an implicit conversion to the associated gimple stmt.
> Having this conversion makes the rest of the series easier to write,
> but since the class goes away
On Tue, Jul 24, 2018 at 11:57 AM Richard Sandiford
wrote:
>
> This patch makes vect_is_simple_use pass back a stmt_vec_info to
> those callers that want it. Most users only need the stmt_vec_info
> but some need the gimple stmt too.
Hmm. Unfortunately it's not redundant for dt_extern ...
> It'
On Tue, Jul 24, 2018 at 11:58 AM Richard Sandiford
wrote:
>
> This patch makes vect_finish_replace_stmt and vect_finish_stmt_generation
> return the stmt_vec_info for the vectorised statement, so that the caller
> doesn't need a separate vinfo_for_stmt to get at it.
>
> This involved changing the
On Tue, Jul 24, 2018 at 11:58 AM Richard Sandiford
wrote:
>
> This patch changes STMT_VINFO_RELATED_STMT from a gimple stmt to a
> stmt_vec_info.
OK.
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vectorizer.h (_stmt_vec_info::related_stmt): Change from
> a gimple stmt to
On Tue, Jul 24, 2018 at 11:58 AM Richard Sandiford
wrote:
>
> This patch changes STMT_VINFO_VEC_STMT from a gimple stmt to a
> stmt_vec_info and makes the vectorizable_* routines pass back
> a stmt_vec_info to vect_transform_stmt.
OK, but - I don't think we ever "use" that stmt_info on vectorized
On Tue, Jul 24, 2018 at 11:59 AM Richard Sandiford
wrote:
>
> This patch changes STMT_VINFO_REDUC_DEF from a gimple stmt to a
> stmt_vec_info.
OK
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vectorizer.h (_stmt_vec_info::reduc_def): Change from
> a gimple stmt to a stmt_
On Tue, Jul 24, 2018 at 11:59 AM Richard Sandiford
wrote:
>
> This patch changes SLP_TREE_VEC_STMTS from a vec to a
> vec. This involved making the same change to the
> phis vector in vectorizable_reduction, since SLP_TREE_VEC_STMTS is
> spliced into it here:
>
> phis.splice (SLP_TREE_VEC_STMTS
On Tue, Jul 24, 2018 at 11:59 AM Richard Sandiford
wrote:
>
> This patch changes LOOP_VINFO_REDUCTIONS from an auto_vec
> to an auto_vec. It also changes the associated
> vect_force_simple_reduction so that it takes and returns stmt_vec_infos
> instead of gimple stmts.
OK.
Highlights that reduc
On Tue, Jul 24, 2018 at 12:01 PM Richard Sandiford
wrote:
>
> This patch changes SLP_TREE_SCALAR_STMTS from a vec to
> a vec. It's longer than the previous conversions
> but mostly mechanical.
OK. I don't remember exactly but vect_external_def SLP nodes have
empty stmts vector then? I realize
On Tue, Jul 24, 2018 at 12:01 PM Richard Sandiford
wrote:
>
> This patch makes vect_dr_stmt return a stmt_vec_info instead of a
> gimple stmt. Rather than retain a separate gimple stmt variable
> in cases where both existed, the patch replaces uses of the gimple
> variable with the uses of the st
On Tue, Jul 24, 2018 at 12:01 PM Richard Sandiford
wrote:
>
> This patch changes {REDUC,DR}_GROUP_{FIRST,NEXT} element from a
> gimple stmt to stmt_vec_info.
OK.
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vectorizer.h (_stmt_vec_info::first_element): Change from
> a gi
On Tue, Jul 24, 2018 at 12:02 PM Richard Sandiford
wrote:
>
> This patch changes STMT_VINFO_SAME_DR_STMT from a gimple stmt to a
> stmt_vec_info.
OK.
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vectorizer.h (_stmt_vec_info::same_dr_stmt): Change from
> a gimple stmt to
On Tue, Jul 24, 2018 at 12:01 PM Richard Sandiford
wrote:
>
> This patch changes the SLP lists grouped_stores and reduction_chains
> from auto_vec to auto_vec. It was easier
> to do them together due to the way vect_analyze_slp is structured.
OK.
>
> 2018-07-24 Richard Sandiford
>
> gcc/
>
On Tue, Jul 24, 2018 at 12:02 PM Richard Sandiford
wrote:
>
> This patch changes LOOP_VINFO_MAY_MISALIGN_STMTS from an
> auto_vec to an auto_vec.
OK.
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vectorizer.h (_loop_vec_info::may_misalign_stmts): Change
> from an auto_vec
On Tue, Jul 24, 2018 at 12:02 PM Richard Sandiford
wrote:
>
> This patch makes stmt_info_for_cost carry a stmt_vec_info instead
> of a gimple stmt. The structure is internal to the vectoriser,
> so targets aren't affected.
OK
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vectori
On Tue, Jul 24, 2018 at 12:03 PM Richard Sandiford
wrote:
>
> ...and also make vect_find_last_scalar_stmt_in_slp return a stmt_vec_info.
OK
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vectorizer.h (get_earlier_stmt, get_later_stmt): Take and
> return stmt_vec_infos rath
On Tue, Jul 24, 2018 at 12:03 PM Richard Sandiford
wrote:
>
> If we use stmt_vec_infos to represent statements in the vectoriser,
> it's then more natural to use dyn_cast when processing the statement
> as an assignment, call, etc. This patch does that in a few more places.
OK.
>
> 2018-07-24
On Tue, Jul 24, 2018 at 12:03 PM Richard Sandiford
wrote:
>
> Various places called vect_dr_stmt or vinfo_for_stmt multiple times
> on the same input. This patch makes them reuse the earlier result.
> It also splits a couple of single vinfo_for_stmt calls out into
> separate statements so that th
On Tue, Jul 24, 2018 at 12:04 PM Richard Sandiford
wrote:
>
> This first part makes functions use stmt_vec_infos instead of
> gimple stmts in cases where the stmt_vec_info was already available
> and where the change is mechanical. Most of it is just replacing
> "stmt" with "stmt_info".
OK
>
>
On 24/07/18 17:30, Richard Biener wrote:
> On July 24, 2018 5:50:33 PM GMT+02:00, Ramana Radhakrishnan
> wrote:
>> On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener
>> wrote:
>>>
>>> Status
>>> ==
>>>
>>> The GCC 8 branch is frozen for preparation of the GCC 8.2 release.
>>> All changes to th
On 24/07/18 18:26, Richard Biener wrote:
> On Mon, Jul 9, 2018 at 6:40 PM Richard Earnshaw
> wrote:
>>
>>
>> This patch defines a new intrinsic function
>> __builtin_speculation_safe_value. A generic default implementation is
>> defined which will attempt to use the backend pattern
>> "speculatio
On Wed, Jul 25, 2018 at 10:28:30AM +0200, Richard Biener wrote:
> On Tue, Jul 24, 2018 at 7:18 PM Segher Boessenkool
> wrote:
> >
> > This patch allows combine to combine two insns into two. This helps
> > in many cases, by reducing instruction path length, and also allowing
> > further combinati
Hi Tamar,
On Mon, 23 Jul 2018 at 17:56, Tamar Christina wrote:
>
> Hi All,
>
> My previous patch changed arm_can_change_mode_class to allow subregs of
> 64bit registers on arm big-endian. However it seems that we can't do this
> because a the data in 64 bit VFP registers are stored in little-end
On Wed, 25 Jul 2018, Richard Earnshaw (lists) wrote:
> On 24/07/18 17:30, Richard Biener wrote:
> > On July 24, 2018 5:50:33 PM GMT+02:00, Ramana Radhakrishnan
> > wrote:
> >> On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener
> >> wrote:
> >>>
> >>> Status
> >>> ==
> >>>
> >>> The GCC 8 bran
On Tue, Jul 24, 2018 at 12:04 PM Richard Sandiford
wrote:
>
> This second part handles the less mechnical cases, i.e. those that don't
> just involve swapping a gimple stmt for an existing stmt_vec_info.
OK.
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vect-loop.c (vect_analyze_
On Tue, Jul 24, 2018 at 12:05 PM Richard Sandiford
wrote:
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vect-loop.c (vect_analyze_scalar_cycles_1): Change the type
> of the worklist from a vector of gimple stmts to a vector of
> stmt_vec_infos.
> * tree-vect
On 24/07/18 22:55, Steve Ellcey wrote:
> On Tue, 2018-07-24 at 22:04 +0100, James Greenhalgh wrote:
>>
>>
>> I'd say this patch isn't desirable for trunk. I'd be interested in use cases
>> that need a static decision on presence of LSE that are not better expressed
>> using higher level language
On Tue, Jul 24, 2018 at 12:05 PM Richard Sandiford
wrote:
>
> This first (less mechanical) part handles cases that involve changes in
> the callers or non-trivial changes in the functions themselves.
OK
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vect-data-refs.c (vect_describe
On Tue, Jul 24, 2018 at 12:06 PM Richard Sandiford
wrote:
>
> This patch makes vect_record_max_nunits and vect_record_base_alignment
> take a stmt_vec_info instead of a vec_info/gimple pair.
OK
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vect-data-refs.c (vect_record_base_align
On Tue, Jul 24, 2018 at 12:06 PM Richard Sandiford
wrote:
>
> This second part handles the mechanical change from a gimple stmt
> argument to a stmt_vec_info argument. It updates the function
> comments if they referred to the argument by name, but it doesn't
> try to retrofit mentions to other f
On Tue, Jul 24, 2018 at 12:06 PM Richard Sandiford
wrote:
>
> This patch makes vect_get_vec_def_for_stmt_copy take a vec_info
> rather than a vect_def_type. If the vector operand passed in is
> defined in the vectorised region, we should look for copies in
> the normal way. If it's defined in an
On Tue, Jul 24, 2018 at 12:06 PM Richard Sandiford
wrote:
>
> vect_pattern_recog_1 took a gimple_stmt_iterator as argument, but was
> only interested in the gsi_stmt, not anything else. This patch makes
> the associated routines operate directly on stmt_vec_infos.
OK
>
> 2018-07-24 Richard San
On Tue, Jul 24, 2018 at 12:07 PM Richard Sandiford
wrote:
>
> This patch adds a pattern_stmt_p field to stmt_vec_info, so that it's
> possible to tell whether the statement is a pattern statement without
> referring to other statements. The new field goes in what was
> previously a hole in the st
On Tue, Jul 24, 2018 at 12:08 PM Richard Sandiford
wrote:
>
> Alignment information is really a property of a stmt_vec_info
> (and the way we want to vectorise it) rather than the original scalar dr.
> I think that was true even before the recent dr sharing.
But that is only so as long as we hand
On Tue, Jul 24, 2018 at 12:08 PM Richard Sandiford
wrote:
>
> This patch makes various routines (mostly in tree-vect-data-refs.c)
> take stmt_vec_infos rather than data_references. The affected routines
> are really dealing with the way that an access is going to vectorised
> for a particular stm
On Wed, Jul 25, 2018 at 11:49 AM Richard Earnshaw (lists)
wrote:
>
> On 24/07/18 18:26, Richard Biener wrote:
> > On Mon, Jul 9, 2018 at 6:40 PM Richard Earnshaw
> > wrote:
> >>
> >>
> >> This patch defines a new intrinsic function
> >> __builtin_speculation_safe_value. A generic default impleme
On Wed, Jul 25, 2018 at 11:50 AM Segher Boessenkool
wrote:
>
> On Wed, Jul 25, 2018 at 10:28:30AM +0200, Richard Biener wrote:
> > On Tue, Jul 24, 2018 at 7:18 PM Segher Boessenkool
> > wrote:
> > >
> > > This patch allows combine to combine two insns into two. This helps
> > > in many cases, by
This will allow std::mutex and std::lock_guard to be used elsewhere in
the library without pulling in the whole of .
Previously the whole of was conditional on the
_GLIBCXX_USE_C99_STDINT_TR1 macro, but only the std::unique_lock members
that use facilities should depend on that. std::mutex only
On Tue, Jul 24, 2018 at 10:55 PM, Steve Ellcey wrote:
> On Tue, 2018-07-24 at 22:04 +0100, James Greenhalgh wrote:
>>
>>
>> I'd say this patch isn't desirable for trunk. I'd be interested in use cases
>> that need a static decision on presence of LSE that are not better expressed
>> using higher l
On 24/07/18 22:12 +0100, Jonathan Wakely wrote:
This is missing the synchronized_pool_resource and
unsynchronized_pool_resource classes but is otherwise complete.
This is a new implementation, not based on the existing code in
, but memory_resource and
polymorphic_allocator ended up looking almo
On Tue, Jul 24, 2018 at 04:11:11PM -0300, Alexandre Oliva wrote:
> On Jul 24, 2018, Tom de Vries wrote:
>
> > This patch adds fake uses of user variables at the point where they go out
> > of
> > scope, to keep user variables inspectable throughout the application.
>
> I suggest also adding suc
Richard Biener writes:
> On Tue, Jul 24, 2018 at 11:58 AM Richard Sandiford
> wrote:
>>
>> This patch changes STMT_VINFO_VEC_STMT from a gimple stmt to a
>> stmt_vec_info and makes the vectorizable_* routines pass back
>> a stmt_vec_info to vect_transform_stmt.
>
> OK, but - I don't think we ever
On Tue, Jul 24, 2018 at 05:04:06PM +0200, Tom de Vries wrote:
>
> > +Add artificial use for each local variable at the end of the
> > declaration scope
>
> Is this a better option description?
Yes (with a period at the end). Or perhaps "its" instead of "the".
Looks ok to me, just would like to
Hi All,
Attached is an updated patch that clarifies some of the comments in the patch
and adds comments to the individual testcases
as requested.
Ok for trunk?
Thanks,
Tamar
gcc/
2018-07-25 Jeff Law
Richard Sandiford
Tamar Christina
PR target/86486
HI Alexandre,
Thanks for the review. Attached is the updated patch and new changelog below:
Thanks,
Tamar
gcc/
2018-07-25 Tamar Christina
PR target/86486
* configure.ac: Add stack-clash-protection-guard-size.
* doc/install.texi: Document it.
* config.in (DEFAU
Hi All,
Attached an updated patch which documents what the test cases are expecting as
requested.
Ok for trunk?
Thanks,
Tamar
gcc/
2018-07-25 Tamar Christina
PR target/86486
* config/aarch64/aarch64.h (STACK_CLASH_OUTGOING_ARGS,
STACK_DYNAMIC_OFFSET): New.
*
Richard Biener writes:
> On Tue, Jul 24, 2018 at 12:07 PM Richard Sandiford
> wrote:
>>
>> This patch adds a pattern_stmt_p field to stmt_vec_info, so that it's
>> possible to tell whether the statement is a pattern statement without
>> referring to other statements. The new field goes in what w
Richard Biener writes:
> On Tue, Jul 24, 2018 at 12:08 PM Richard Sandiford
> wrote:
>>
>> This patch makes various routines (mostly in tree-vect-data-refs.c)
>> take stmt_vec_infos rather than data_references. The affected routines
>> are really dealing with the way that an access is going to v
On Tue, 24 Jul 2018, Tom de Vries wrote:
> On Tue, Jul 24, 2018 at 02:34:26PM +0200, Tom de Vries wrote:
> > On 07/24/2018 01:46 PM, Jakub Jelinek wrote:
> > > On Tue, Jul 24, 2018 at 01:37:32PM +0200, Tom de Vries wrote:
> > >> Another drawback is that the fake uses confuse the unitialized warnin
On Wed, Jul 25, 2018 at 1:41 PM Richard Biener wrote:
>
> On Tue, 24 Jul 2018, Tom de Vries wrote:
>
> > On Tue, Jul 24, 2018 at 02:34:26PM +0200, Tom de Vries wrote:
> > > On 07/24/2018 01:46 PM, Jakub Jelinek wrote:
> > > > On Tue, Jul 24, 2018 at 01:37:32PM +0200, Tom de Vries wrote:
> > > >> A
On Wed, Jul 25, 2018 at 1:09 PM Richard Sandiford
wrote:
>
> Richard Biener writes:
> > On Tue, Jul 24, 2018 at 12:07 PM Richard Sandiford
> > wrote:
> >>
> >> This patch adds a pattern_stmt_p field to stmt_vec_info, so that it's
> >> possible to tell whether the statement is a pattern statement
Hi.
It's obvious fix of return type. It's the same what's
in gcc/config/rs6000/rs6000.h.
Martin
gcc/ChangeLog:
2018-07-25 Martin Liska
* config/powerpcspe/powerpcspe-protos.h (rs6000_loop_align): Fix
return type.
---
gcc/config/powerpcspe/powerpcspe-protos.h | 2 +-
1 file
On Tue, 24 Jul 2018, Richard Biener wrote:
>
> I am testing the following patch to avoid forcing DIEs for a type context
> for method clones late via limbo processing. Instead hang them off
> comp_unit_die if there is no early DIE for the function.
>
> One question is whether the comment "If we
Hello,
I talked about this last year
(https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01063.html and thread),
this tweaks std::vector move assignment to help gcc generate better code
for it.
For this code
#include
#include
typedef std::vector V;
void f(V&a,V&b){a=std::move(b);}
with -O2 -f
On 25/07/18 11:36, Richard Biener wrote:
> On Wed, Jul 25, 2018 at 11:49 AM Richard Earnshaw (lists)
> wrote:
>>
>> On 24/07/18 18:26, Richard Biener wrote:
>>> On Mon, Jul 9, 2018 at 6:40 PM Richard Earnshaw
>>> wrote:
This patch defines a new intrinsic function
__builtin_spe
On 07/24/18 16:50, Richard Biener wrote:
> On Tue, 24 Jul 2018, Bernd Edlinger wrote:
>
>> Hi!
>>
>> This patch makes strlen range computations more conservative.
>>
>> Firstly if there is a visible type cast from type A to B before passing
>> then value to strlen, don't expect the type layout of
On 07/23/2018 05:01 PM, Sudakshina Das wrote:
Hi Sam
On Monday 23 July 2018 11:39 AM, Sam Tebbs wrote:
Hi all,
This patch extends the aarch64_get_lane_zero_extendsi instruction
definition to
also cover DI mode. This prevents a redundant AND instruction from being
generated due to the patter
On 25/07/18 14:38 +0200, Marc Glisse wrote:
Hello,
I talked about this last year
(https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01063.html and thread),
this tweaks std::vector move assignment to help gcc generate better
code for it.
Ah yes, thank for revisiting it.
For this code
#include
> On Jul 25, 2018, at 12:50 AM, Jeff Law wrote:
>
...
>>> It did. See TARGET_CUSTOM_FUNCTION_DESCRIPTORS and the (relatively few)
>>> ports that define it.
>>
>> Hmmm, I completely failed to make that connection from the docs -- the
>> whole description of that hook is pretty gibberishy
On Wed, 25 Jul 2018, Jonathan Wakely wrote:
_M_copy_data is not really needed, we could add a defaulted assignment
operator, or remove the move constructor (and call a new _M_clear() from
the 2 users), etc. However, it seemed the least intrusive, the least likely
to have weird consequences.
Hi Kyrill,
Using memory_operand worked, the issues I encountered when using it in
earlier versions of the patch must have been due to the missing test
on address_operand in the preparation statements which I added later.
Please find an updated patch in attachment. ChangeLog entry is as
follows:
*
Hi.
Target clones have DECL_ARTIFICIAL set to 1, but we want to
provide --coverage for that. With patched GCC on can see:
-:0:Source:pr85370.c
-:0:Graph:pr85370.gcno
-:0:Data:pr85370.gcda
-:0:Runs:1
-:0:Programs:1
-:1:__attri
Hi.
It fixes couple of very similar issues. Currently we handle GOTO
expression, but it's not easy to find these in GIMPLE middle-end.
The patch fixes that.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Will install in couple of days if no objection.
Martin
gcc/Chan
Hi.
Last patch from GCOV series is about not streaming of redundant lines
for a basic-block. It helps to fix few issues.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Will install in couple of days if no objection.
Martin
gcc/ChangeLog:
2018-07-25 Martin Liska
On Wed, Jul 25, 2018 at 2:41 PM Richard Earnshaw (lists)
wrote:
>
> On 25/07/18 11:36, Richard Biener wrote:
> > On Wed, Jul 25, 2018 at 11:49 AM Richard Earnshaw (lists)
> > wrote:
> >>
> >> On 24/07/18 18:26, Richard Biener wrote:
> >>> On Mon, Jul 9, 2018 at 6:40 PM Richard Earnshaw
> >>> wro
On Tue, 2018-07-24 at 17:18 +, Segher Boessenkool wrote:
> This patch allows combine to combine two insns into two. This helps
> in many cases, by reducing instruction path length, and also allowing
> further combinations to happen. PR85160 is a typical example of code
> that it can improve.
All the patches in this series look fine.
Thanks,
Andrew
* Claudiu Zissulescu [2018-07-16 15:29:42 +0300]:
> From: claziss
>
> gcc/
> 2017-06-14 Claudiu Zissulescu
>
> * config/arc/arc.h (ADDITIONAL_REGISTER_NAMES): Add additional
> register names.
> ---
> gcc/config/arc/arc
On Wed, Jul 25, 2018 at 3:38 PM Martin Liška wrote:
>
> Hi.
>
> Target clones have DECL_ARTIFICIAL set to 1, but we want to
> provide --coverage for that. With patched GCC on can see:
>
> -:0:Source:pr85370.c
> -:0:Graph:pr85370.gcno
> -:0:Data:pr85370.gcda
>
Hi,
as discussed with Martin, this patch consolidates -Warray-bounds into an
alias of -Warray-bounds=1.
Bootstrapped on x86_64-linux, no regressions.
Please apply if it's OK.
Franz.
gcc/ChangeLog:
2018-07-25 Franz Sirl
* common.opt: Alias -Warray-bounds to -Warray-bounds=1.
On Wed, Jul 25, 2018 at 09:47:31AM -0400, David Malcolm wrote:
> > +/* Return whether X is just a single set, with the source
> > + a general_operand. */
> > +static bool
> > +is_just_move (rtx x)
> > +{
> > + if (INSN_P (x))
> > +x = PATTERN (x);
> > +
> > + return (GET_CODE (x) == SET &&
There's a small leak in class optrecord_json_writer, which shows
up as a new leak in "make selftest-valgrind" as:
==50133== 40 bytes in 1 blocks are definitely lost in loss record 27 of 672
==50133==at 0x4A0645D: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==50133==b
On 07/25/2018 02:34 AM, Richard Biener wrote:
On Wed, Jul 25, 2018 at 4:07 AM Martin Sebor wrote:
The very large option argument enhancement committed last week
inadvertently introduced an assumption about the LP64 data model
that makes the -Wxxx-larger-than options have a different effect
at
On 07/25/2018 07:16 AM, Paul Koning wrote:
Non-executable stacks are a very good thing.
That said, I also looked at the target hook documentation and was
left without any clue whatsoever. It sure isn't clear what powers of
two have to do with descriptors, or what descriptors have to do with
su
On Wed, Jul 25, 2018 at 08:54:13AM -0600, Martin Sebor wrote:
> I don't mean for the special value to be used except internally
> for the defaults. Otherwise, users wanting to override the default
> will choose a value other than it. I'm happy to document it in
> the .opt file for internal users
On Tue, 2018-07-24 at 16:11 +0200, Richard Biener wrote:
> On Mon, Jul 23, 2018 at 9:20 PM David Malcolm
> wrote:
> >
> > On Mon, 2018-07-23 at 11:46 +0200, Richard Biener wrote:
> > > On Fri, Jul 20, 2018 at 6:27 PM David Malcolm > > m>
> > > wrote:
> > > >
> > > > This patch adds a Python 3 m
Pushed. Thank you for your review,
Claudiu
From: Andrew Burgess [andrew.burg...@embecosm.com]
Sent: Wednesday, July 25, 2018 3:49 PM
To: Claudiu Zissulescu
Cc: gcc-patches@gcc.gnu.org; francois.bed...@synopsys.com; claziss
Subject: Re: [PATCH 1/4] [ARC] Add
Hi Thomas,
Thanks for the review!
> >
> > I don't believe the TARGET_FP16 guard to be needed, because the
> > pattern doesn't actually generate code and requires another pattern
> > for that, and a reg to reg move should always be possible anyway. So
> > allowing the force to register here is saf
The fortran FE incorrectly records the line locations of combined acc
loop directives when it lowers the construct to gimple. Usually this
isn't a problem because the fortran FE is able to report problems with
acc loops itself. However, there will be inaccuracies if the ME tries
to use those locati
This patch series extends -fopt-info-note-omp to include OpenACC loop
diagnostics when it is used in conjunction with -fopenacc. At present,
the diagnostics are limited to reporting how OpenACC loops are
partitioned, e.g., seq, gang, worker or vector. The major advantage of
this diagnostics is that
Like the fortran FE, the C++ FE doesn't set the expr_location of the
split acc loop in combined acc parallel/kernels loop directives. This
only happens for with combined directives, otherwise
cp_parser_omp_construct would be responsible for setting the
location. After fixing this bug, I was able to
This patch teaches GCC to inform the user how it assigned parallelism
to each OpenACC loop at compile time using the -fopt-info-note-omp
flag. For instance, given the acc parallel loop nest:
#pragma acc parallel loop
for (...)
#pragma acc loop vector
for (...)
GCC will report somthing
On Wed, Jul 25, 2018 at 08:29:17AM -0700, Cesar Philippidis wrote:
> The fortran FE incorrectly records the line locations of combined acc
> loop directives when it lowers the construct to gimple. Usually this
> isn't a problem because the fortran FE is able to report problems with
> acc loops itse
On 07/25/2018 08:32 AM, Marek Polacek wrote:
> On Wed, Jul 25, 2018 at 08:29:17AM -0700, Cesar Philippidis wrote:
>> The fortran FE incorrectly records the line locations of combined acc
>> loop directives when it lowers the construct to gimple. Usually this
>> isn't a problem because the fortran F
On 07/25/2018 08:57 AM, Jakub Jelinek wrote:
On Wed, Jul 25, 2018 at 08:54:13AM -0600, Martin Sebor wrote:
I don't mean for the special value to be used except internally
for the defaults. Otherwise, users wanting to override the default
will choose a value other than it. I'm happy to document
Hi!
OpenMP 5.0 allows the teams construct, previously required to be strictly
nested (i.e. without any OpenMP construct in between) and even with no user
code in between inside of target construct, also as a host construct that is
not nested in any OpenMP construct at all. The primary goal is for
On 07/18/2018 06:43 PM, Jakub Jelinek wrote:
On Wed, Jul 18, 2018 at 06:00:20PM -0400, Nathan Sidwell wrote:
So cool! Thanks.
Ok for both patches or just this one?
both are ok, sorry for delay (vacation), thanks for doing that!
nathan
--
Nathan Sidwell
1 - 100 of 123 matches
Mail list logo
