Hello Julia,
On 08 Nov 12:32, Koval, Julia wrote:
> Hi, this patch enables VAESDEC instruction from VAES isaset, defined here:
> https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-extensions-programming-reference.pdf
>
> Ok for trunk?
Your patch is OK. I've
On 12/06/2017 04:50 PM, Jeff Law wrote:
Richi's fix for 83202 fixed a few other bugs in the BZ database. This
patch adds regression tests for the 3 I trivially found.
Committing to the trunk.
The test submitted in pr82286 relied on the ERROR macro being
defined to trigger the false positive
On 12/06/2017 03:58 PM, Jeff Law wrote:
On 12/06/2017 12:41 PM, Jeff Law wrote:
On 12/06/2017 12:27 PM, Martin Sebor wrote:
For reference, I committed r255450 to avoid the test failure
reported on the arm-none-eabi target. The warning is valid
but unrelated to the purpose of the test so I prun
Richi's fix for 83202 fixed a few other bugs in the BZ database. This
patch adds regression tests for the 3 I trivially found.
Committing to the trunk.
Jeff
commit 813ce64afdf420b8d5e3fee59473f2527c5d0d4d
Author: Jeff Law
Date: Wed Dec 6 18:46:01 2017 -0500
PR tree-optimization/
On 12/06/2017 12:41 PM, Jeff Law wrote:
> On 12/06/2017 12:27 PM, Martin Sebor wrote:
>> For reference, I committed r255450 to avoid the test failure
>> reported on the arm-none-eabi target. The warning is valid
>> but unrelated to the purpose of the test so I pruned it from
>> its output.
>>
>> M
Hello,
ping for https://gcc.gnu.org/ml/gcc-patches/2017-11/msg02537.html
> On Nov 30, 2017, at 10:18 , Olivier Hainque wrote:
>
> Bootstrap is currently broken with Ada on x86_64-windows using SEH exceptions,
>PR ada/81470
>* dwarf2out.c (dwarf2out_do_cfi_startproc): Only emi
OK.
On Fri, Dec 1, 2017 at 7:13 PM, Jakub Jelinek wrote:
> Hi!
>
> As the testcase shows, we weren't diagnosing the foo case in the testcase
> and would just silently overwrite old DECL_INITIAL with error_mark_node
> and ICE later on. Fixed thusly, bootstrapped/regtested on x86_64-linux
> and i6
On Fri, Dec 1, 2017 at 7:42 AM, Bernd Edlinger
wrote:
> this version of the patch improves the heuristic check to take the
> target hook into account, to handle cases correctly when both or only
> one parameter is _not_ promoted to int.
In looking at this, I discovered that the argument to
promot
I would like to backport the following patch to the GCC 7 branch.
PR80101: Fix ICE in store_data_bypass_p
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00953.html
This patch has been bootstrapped and regression tested on the
GCC 7 branch.
Is this ok for backporting to GCC 7?
In this testcase, we consider the initializer of b to decide if it's
value-dependent, but the initializer mentions b, so we were recursing
infinitely. But if we're interested in the address, we don't care
about the value; we already handle that appropriately in the constexpr
code, this patch updat
Hi!
Aggregate assignments and clears aren't in GIMPLE represented as calls,
and while often they expand inline, sometimes we emit libcalls for them.
This patch allows us to tail call those libcalls if there is nothing
after them. The patch changes the tailcall pass, so that it recognizes
a = b; a
On 10/23/2017 11:20 AM, Richard Sandiford wrote:
> This patch changes various bits of state related to argument sizes so
> that they have type poly_int64 rather than HOST_WIDE_INT. This includes:
>
> - incoming_args::pops_args and incoming_args::size
> - rtl_data::outgoing_args_size
> - pending_s
On 11/13/2017 05:04 PM, Richard Sandiford wrote:
> Richard Sandiford writes:
>> Richard Sandiford writes:
>>> This patch adds a new "poly_int" class to represent polynomial integers
>>> of the form:
>>>
>>> C0 + C1*X1 + C2*X2 ... + Cn*Xn
>>>
>>> It also adds poly_int-based typedefs for offsets
On 12/06/2017 12:58 PM, Martin Sebor wrote:
> On 12/06/2017 12:41 PM, Jeff Law wrote:
>> On 12/06/2017 12:27 PM, Martin Sebor wrote:
>>> For reference, I committed r255450 to avoid the test failure
>>> reported on the arm-none-eabi target. The warning is valid
>>> but unrelated to the purpose of t
On 10/23/2017 11:11 AM, Richard Sandiford wrote:
> This patch changes the types of the bit offsets and sizes returned
> by get_ref_base_and_extent to poly_int64.
>
> There are some callers that can't sensibly operate on polynomial
> offsets or handle cases where the offset and size aren't known
>
On 12/06/2017 12:41 PM, Jeff Law wrote:
On 12/06/2017 12:27 PM, Martin Sebor wrote:
For reference, I committed r255450 to avoid the test failure
reported on the arm-none-eabi target. The warning is valid
but unrelated to the purpose of the test so I pruned it from
its output.
Martin
Index: gc
On 12/06/2017 12:27 PM, Martin Sebor wrote:
> For reference, I committed r255450 to avoid the test failure
> reported on the arm-none-eabi target. The warning is valid
> but unrelated to the purpose of the test so I pruned it from
> its output.
>
> Martin
>
> Index: gcc/testsuite/ChangeLog
> ===
Hi!
When looking at the rs6000_store_data_bypass_p stuff, I've noticed that
it accepts PARALLELs containing not just SETs and CLOBBERs like
store_data_bypass_p, but also USEs. Given that it is something that
single_set also ignores, I think fixing store_data_bypass_p is the
right fix here.
Boots
Hi!
We don't really care about gsi after this statement, and GSI_SAME_STMT
on gsi_insert_after is wrong if the bb we're inserting into is empty.
So, either we'd need to use the gsi_insert_before with GSI_SAME_STMT in that
case by tweaking the if, or we just tweak the last argument.
Bootstrapped/r
For reference, I committed r255450 to avoid the test failure
reported on the arm-none-eabi target. The warning is valid
but unrelated to the purpose of the test so I pruned it from
its output.
Martin
Index: gcc/testsuite/ChangeLog
On Tue, Dec 05, 2017 at 02:44:22PM +0100, Jakub Jelinek wrote:
> As mentioned in the PR, while (T)(P + A) - (T)P -> (T) A
> shouldn't introduce UB when it wasn't there earlier,
> (T)P - (T)(P + A) -> -(T) A
> and
> (T)(P + A) - (T)(P + B) -> (T)A - (T)B
> can, so if the conversion to T isn't wideni
On 10/23/2017 11:10 AM, Richard Sandiford wrote:
> This patch changes SUBREG_BYTE from an int to a poly_int.
> Since valid SUBREG_BYTEs must be contained within the mode of the
> SUBREG_REG, the required range is the same as for GET_MODE_SIZE,
> i.e. unsigned short. The patch therefore uses poly_u
On Tue, Dec 5, 2017 at 5:11 PM, David Malcolm wrote:
> + const char *suggestion_str = IDENTIFIER_POINTER (binding->id);
> + if (name_reserved_for_implementation_p (suggestion_str))
You might add an overload that takes an identifier.
OK either way.
Jason
On 10/23/2017 11:07 AM, Richard Sandiford wrote:
> This patch changes the MEM_OFFSET and MEM_SIZE memory attributes
> from HOST_WIDE_INT to poly_int64. Most of it is mechanical,
> but there is one nonbovious change in widen_memory_access.
> Previously the main while loop broke with:
>
> /*
This patch by Than McIntosh removes -fplan9-extensions from the CFLAGS
used for libgo. It is no longer needed since the runtime was
converted from C to Go. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
===
On 10/23/2017 11:17 AM, Richard Sandiford wrote:
> This patch makes get_inner_reference and ptr_difference_const return the
> bit size and bit position as poly_int64s rather than HOST_WIDE_INTS.
> The non-mechanical changes were handled by previous patches.
>
>
> 2017-10-23 Richard Sandiford
>
On 5 December 2017 at 19:02, Bernhard Reutner-Fischer
wrote:
> On 16 June 2010 at 14:56, Janus Weil wrote:
Regtested on x86_64-unknown-linux-gnu. Ok for trunk?
>>>
>>> OK. Kudos to Dominique for finding it and thanks, Janus, for fixing it.
>>
>> Thanks. Committed as r160834.
>
> @@ -459
On 12/05/2017 07:49 AM, Jakub Jelinek wrote:
On Mon, Dec 04, 2017 at 11:52:01AM +0100, Jakub Jelinek wrote:
On Wed, Nov 29, 2017 at 05:21:22PM -0500, Vladimir Makarov wrote:
The following patch fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80818
The patch was successfully tested
Hi,
Add support for gimple folding of splat_u{8,16,32}.
Testcase coverage is primarily handled by existing tests
testsuite/gcc.target/powerpc/fold-vec-splat_*.c
One new test added to verify we continue to receive
an 'invalid argument, must be a 5-bit immediate' error
when we try to splat a non
On Wed, Dec 06, 2017 at 09:20:15AM -0700, Martin Sebor wrote:
> Attached is a patch with the comment updated/simplified.
> The tests do the job they need to do today so I just removed
> the useless attribute but otherwise left them unchanged. If
> you would like to enhance them in some way please
Hi Tamar,
On 06/11/17 16:52, Tamar Christina wrote:
Hi All,
This patch adds the needed machinery to generate the appropriate
.arch and .arch_extension directives per function.
Borrowing from AArch64 this is only done when it's required (i.e. when
the directives to be set differ from the curren
Attached is a patch with the comment updated/simplified.
The tests do the job they need to do today so I just removed
the useless attribute but otherwise left them unchanged. If
you would like to enhance them in some way please feel free.
Martin
On 11/20/2017 02:56 PM, Jakub Jelinek wrote:
On
On December 6, 2017 5:12:08 PM GMT+01:00, Bin Cheng wrote:
>Hi,
>The loop interchange pass reuses option -floop-interchange from
>GRAPHITE, this patch
>adjusts all affected GRAPHITE tests by changing the option to
>-floop-nest-optimize.
>Test result checked with/without loop interchange. Is it OK
Hi,
The loop interchange pass reuses option -floop-interchange from GRAPHITE, this
patch
adjusts all affected GRAPHITE tests by changing the option to
-floop-nest-optimize.
Test result checked with/without loop interchange. Is it OK?
Thanks,
bin
gcc/testsuite
2017-12-06 Bin Cheng
*
On Fri, 2017-11-17 at 12:10 +0200, Boris Kolpackov wrote:
> The below patch adds the -fmacro-prefix-map option that allows
> remapping
> of file names in __FILE__, __BASE_FILE__, and __builtin_FILE(),
> similar
> to how -fdebug-prefix-map allows to do the same for debug
> information.
>
> Addition
This patch makes various bits of code operate directly on the new
VECTOR_CST encoding, instead of using VECTOR_CST_ELT on all elements
of the vector.
Previous patches handled operations that produce a new VECTOR_CST,
while this patch handles things like predicates. It also makes
print_node dump t
After the previous patches, the only remaining uses of build_vector are
in the selftests in tree.c. This patch makes it static and moves it to
the selftest part of the file.
Tested on aarch64-linux-gnu, x86_64-linux-gnu and powerpc64le-linux-gnu.
Also spot-checked on sparc64-linux-gnu. OK to ins
This patch changes gimple_build_vector so that it takes a
tree_vector_builder instead of a size and a vector of trees.
Tested on aarch64-linux-gnu, x86_64-linux-gnu and powerpc64le-linux-gnu.
Also spot-checked on sparc64-linux-gnu. OK to install?
Thanks,
Richard
2017-12-06 Richard Sandiford
This patch makes fold-const.c operate directly on the VECTOR_CST
encoding when folding an operation that has two VECTOR_CST inputs.
Tested on aarch64-linux-gnu, x86_64-linux-gnu and powerpc64le-linux-gnu.
Also spot-checked on sparc64-linux-gnu. OK to install?
Thanks,
Richard
2017-12-06 Richar
This patch switches most build_vector calls over to tree_vector_builder,
using explicit encodings where appropriate. Later patches handle
the remaining uses of build_vector.
Tested on aarch64-linux-gnu, x86_64-linux-gnu and powerpc64le-linux-gnu.
Also spot-checked on sparc64-linux-gnu. OK to ins
This patch makes fold-const.c operate directly on the VECTOR_CST
encoding when folding an operation that has a single VECTOR_CST input.
Tested on aarch64-linux-gnu, x86_64-linux-gnu and powerpc64le-linux-gnu.
Also spot-checked on sparc64-linux-gnu. OK to install?
Thanks,
Richard
2017-12-06 Ric
Richard Biener writes:
> On Thu, Nov 30, 2017 at 2:18 PM, Richard Sandiford
> wrote:
>> Richard Sandiford writes:
>>> Richard Biener writes:
On Wed, Nov 29, 2017 at 12:57 PM, Richard Sandiford
wrote:
> It was clear from the SVE reviews that people were unhappy with how
> "spe
On Wed, 2017-12-06 at 14:40 +, Richard Sandiford wrote:
> David Malcolm writes:
> > On Wed, 2017-11-29 at 11:57 +, Richard Sandiford wrote:
> >
> > [...]
> >
> > I can't really comment on the representation ideas, but I'm always
> > happy to see new selftests...
> >
> > ***
David Malcolm writes:
> On Wed, 2017-11-29 at 11:57 +, Richard Sandiford wrote:
>
> [...]
>
> I can't really comment on the representation ideas, but I'm always
> happy to see new selftests...
>
> *** test_labels ()
>> *** 13954,13959
>> --- 14179,14350
>> ASSERT_FALS
On Wed, Dec 06, 2017 at 11:42:13AM +, Segher Boessenkool wrote:
> In some places in the code we currently use rs6000_cpu_attr, although
> that is a cast from rs6000_tune. This patch changes things to be more
> regular and clearer. Now rs6000_cpu_attr is only used to define the
That should be
On Wed, Dec 6, 2017 at 6:42 AM, Segher Boessenkool
wrote:
> In some places in the code we currently use rs6000_cpu_attr, although
> that is a cast from rs6000_tune. This patch changes things to be more
> regular and clearer. Now rs6000_cpu_attr is only used to define the
>
>
> Segher
>
>
> 2017-
On Wed, Dec 6, 2017 at 6:42 AM, Segher Boessenkool
wrote:
> This splits rs6000_cpu into rs6000_cpu and rs6000_tune. Both are still
> initialised identically, so there is no behaviour change.
>
> Now rs6000_cpu should be set by -mcpu=, and rs6000_tune by -mtune= (but
> both still are set by -mtune
Now also to the list...
-- Forwarded message --
Date: Wed, 6 Dec 2017 14:48:00 +0100 (CET)
From: Richard Biener
To: Martin Jambor
Subject: Re: [PR 83141] Prevent SRA from removing type changing assignment
On Wed, 6 Dec 2017, Martin Jambor wrote:
> Hi,
>
> On Tue, Dec 05 2017,
Hi,
On Tue, Dec 05 2017, Richard Biener wrote:
> On Tue, 5 Dec 2017, Martin Jambor wrote:
>
>> On Tue, Dec 05 2017, Martin Jambor wrote:
>> > On Tue, Dec 05 2017, Martin Jambor wrote:
>> > Hi,
>> >
>> >> Hi,
>> >>
>> >> this is a followup to Richi's
>> >> https://gcc.gnu.org/ml/gcc-patches/2017-11
This patch by Than McIntosh changes the Go frontend code in
Unary_expression::do_get_backend that introduces explicit nil checks
for dereference operations to special case set-and-use-temporary
expressions. For this case it is better to generate an explicit
reference of the temp in the final condit
The following fixes a vectorization issue that appears when trying
to vectorize the bwaves mat_times_vec kernel after interchange was
performed by the interchange pass. That interchange inserts the
following code for the former reduction created by LIM store-motion:
[local count: 161061274]:
On 06/12/17 11:51, Christophe Lyon wrote:
Hi,
On 4 December 2017 at 18:18, Eric Botcazou wrote:
>> Since there are no comments, I'll commit it now.
>
> The idea looks interesting but the timing is a bit more questionable.
>
> --
> Eric Botcazou
Since this was committed (r255384), I've noticed
Hi,
On 4 December 2017 at 18:18, Eric Botcazou wrote:
>> Since there are no comments, I'll commit it now.
>
> The idea looks interesting but the timing is a bit more questionable.
>
> --
> Eric Botcazou
Since this was committed (r255384), I've noticed a regression on
arm-none-linux-gnueabi --wit
Finally, set rs6000_cpu based not on -mtune=, but only -mcpu= and the
defaults.
Segher
2017-12-06 Segher Boessenkool
PR target/43871
* config/rs6000/rs6000.c (rs6000_option_override_internal): Set
rs6000_cpu to the give -mcpu=, or to the default processor.
---
gcc/
This splits rs6000_cpu into rs6000_cpu and rs6000_tune. Both are still
initialised identically, so there is no behaviour change.
Now rs6000_cpu should be set by -mcpu=, and rs6000_tune by -mtune= (but
both still are set by -mtune=, fixed in a later patch in the series).
Also change rs6000_cpu to
In some places in the code we currently use rs6000_cpu_attr, although
that is a cast from rs6000_tune. This patch changes things to be more
regular and clearer. Now rs6000_cpu_attr is only used to define the
Segher
2017-12-06 Segher Boessenkool
* config/rs6000/rs6000.h (rs6000_cpu
Hi,
On 28 November 2017 at 19:40, Thomas Koenig wrote:
> Hello world,
>
> the attached patch implements maxval for characters, an F2003 feature
> that we were missing up to now.
>
> Regression-tested on x86_64-pc-linux-gnu.
>
> OK for trunk?
>
> Regards
>
> Thomas
>
> 2017-11-28 Thomas
> 6.1 Extensions implemented in GNU Fortran
> 7.2 GNU Fortran Compiler Directives
>
> 6.1 describes extension covering legacy code and vendor extensions.
> 7.2 describes other !$GCC directives. Currently, the section is
> mainly calling conventions (CDECL, STDCALL, etc) and library
> macroc (DLLE
Hi,
this is the (hopefully) final implementation of the support for the unrolling
pragma in the C++ front-end. The only change is the handling of USHRT_MAX as
unrolling factor which is now rejected (USHRT_MAX - 1 is the new upper bound).
Tested on x86_64-suse-linux, OK for the mainline?
2017
> You are right, that was a mistake from our side to submit it again. We
> had rediscovered the sequence using our scanning script and I forgot
> that the sequence was harmless in this case. We will update our scripts
> and revert the patch.
OK, thanks in advance.
> The person here with write acc
On Wed, Dec 06, 2017 at 07:54:21AM +0100, Richard Biener wrote:
> On December 5, 2017 10:05:43 PM GMT+01:00, Jakub Jelinek
> wrote:
> >Hi!
> >
> >move_sese_region_to_fn moves a subset of the original loop tree
> >to the dest_cfun (and adds the outermost loop new).
> >Now, some loops might have no
61 matches
Mail list logo
