On 19/10/17 15:00 +0100, Jonathan Wakely wrote:
I made a dumb mistake in the post-inc and post-dec operators for
the path::iterator type, forgetting that _M_cur is sometimes null (for
a single-element path).
* include/experimental/bits/fs_path.h (path::iterator++(int))
(path::ite
Hi Richard,
Attached is a revised patch that makes the downloading of Fortran prerequisites
optional via a new --no-fortran flag that can be passed to
contrib/download_prerequisites as requested in your reply below.
As Jerry mentioned in his response, he has been working on edits to the
top
On 10/02/2017 04:15 PM, Jeff Law wrote:
On 08/10/2017 01:29 PM, Martin Sebor wrote:
diff --git a/gcc/builtins.c b/gcc/builtins.c
index 016f68d..1aa9e22 100644
--- a/gcc/builtins.c
+++ b/gcc/builtins.c
[ ... ]
+
+ if (TREE_CODE (type) == ARRAY_TYPE)
+{
+ /* Return the constant size un
On 19 October 2017 10:03:06 CEST, Bernhard Reutner-Fischer
wrote:
>On Sat, Jun 18, 2016 at 09:46:17PM +0200, Bernhard Reutner-Fischer
>wrote:
>> On December 3, 2015 10:46:09 AM GMT+01:00, Janne Blomqvist
> wrote:
>> >On Tue, Dec 1, 2015 at 6:51 PM, Bernhard Reutner-Fischer
>> > wrote:
>> >> On 1
On 10/20/2017 12:17 PM, Steve Kargl wrote:
> On Fri, Oct 20, 2017 at 07:55:17PM +0100, Paul Richard Thomas wrote:
>>
>> In the last hour, I have added fixes for PRs 82587 and 82589. Please
>> review them together with 82586.
>>
>> I will stop work on Gerhard's PDT bugs until this patch is committed
On 10/20/2017 11:55 AM, Paul Richard Thomas wrote:
> Dear All,
>
> In the last hour, I have added fixes for PRs 82587 and 82589. Please
> review them together with 82586.
>
> I will stop work on Gerhard's PDT bugs until this patch is committed.
> Fortunately, Steve Kargl has proposed fixes for mo
[following up on a discussion at Cauldron]
This is a work-in-progress attempt at retaining source-location
information for uses of variables and for constants: the tree nodes
that don't have an EXPR_LOCATION in our internal representation.
I'm posting the patch now to check that my approach is co
On Oct 20, 2017, at 4:47 PM, Jakub Jelinek wrote:
>
> On Fri, Oct 20, 2017 at 04:41:04PM -0500, Bill Schmidt wrote:
>> As this was rediscovered with PR81294, I've gone ahead with the backport for
>> 6.
>> It does not apply to 5, as the faulty code doesn't exist there.
>
> Well, 5 is closed anyw
On Fri, Oct 20, 2017 at 04:41:04PM -0500, Bill Schmidt wrote:
> As this was rediscovered with PR81294, I've gone ahead with the backport for
> 6.
> It does not apply to 5, as the faulty code doesn't exist there.
Well, 5 is closed anyway.
Jakub
> On Mar 9, 2017, at 2:31 PM, Segher Boessenkool
> wrote:
>
> On Wed, Mar 08, 2017 at 09:47:32AM -0600, Bill Schmidt wrote:
>> As noted by Jakub in
>> https://gcc.gnu.org/ml/gcc-patches/2017-03/msg00183.html,
>> the PowerPC back end incorrectly uses vec_select with 2 elements for a mode
>> tha
Dinka Ranns contributed this feature back in February, but the SD-6
feature-test macro now has a new value to indicate support for this,
so let's update it.
* include/std/chrono (__cpp_lib_chrono): Update macro value to
indicate support for P0505R0.
* testsuite/20_util/dur
This is a simple patch to add a way that the GLIBC team call tell that certain
__float128 built-in functions are available. While previous patches of mine
set __FAST_FP_FMAF128, which could be used for this purpose, this macro just
bumps __FLOAT128_HARDWARE__ to say that the built-in functions are
On 10/20/2017 11:00 AM, Mukesh Kapoor wrote:
Hi,
On 10/20/2017 10:45 AM, Nathan Sidwell wrote:
On 10/20/2017 12:37 PM, Mukesh Kapoor wrote:
Hi,
This patch fixes https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80955.
Handle user-defined literals correctly in lex_string(). An empty
string follo
On Fri, Oct 20, 2017 at 2:15 PM, Joseph Myers wrote:
> This is PR target/52451.
>
> A testcase (conditional on the fenv_exceptions effective-target) that
> ordered comparisons with quiet NaNs set FE_INVALID would be a good idea,
> but it would need XFAILing for powerpc (bug 58684) and s390 (bug 7
Hello Jakub, Uroš, Jakub
On 04 Oct 21:35, Jakub Jelinek wrote:
> Hi!
>
> The following patch tweaks the TImode vector shifts similarly
> to the earlier vector shift patch, so that for shifts by immediate
> we can accept a memory input. Additionally, it removes the vec_shl_*
> expander, because th
On Fri, Oct 20, 2017 at 07:55:17PM +0100, Paul Richard Thomas wrote:
>
> In the last hour, I have added fixes for PRs 82587 and 82589. Please
> review them together with 82586.
>
> I will stop work on Gerhard's PDT bugs until this patch is committed.
> Fortunately, Steve Kargl has proposed fixes
Dear All,
In the last hour, I have added fixes for PRs 82587 and 82589. Please
review them together with 82586.
I will stop work on Gerhard's PDT bugs until this patch is committed.
Fortunately, Steve Kargl has proposed fixes for most of them :-)
Cheers
Paul
2017-10-20 Paul Thomas
PR f
On Thu, Oct 19, 2017 at 7:03 PM, Sandra Loosemore
wrote:
> This is the set of nios2 optimization patches that I've previously
> mentioned in these threads:
>
> https://gcc.gnu.org/ml/gcc/2017-10/msg00016.html
> https://gcc.gnu.org/ml/gcc-patches/2017-10/msg00957.html
>
> To give an overview of wha
On 10/20/2017 02:56 AM, Jakub Jelinek wrote:
On Thu, Oct 19, 2017 at 08:03:45PM -0600, Sandra Loosemore wrote:
A harder problem is that doing the high/lo_sum splitting in expand
inhibits subsequent optimizations. One such problem arises when you
have accesses to multiple fields in a static stru
This patch to libgo supports 64-bit DWARF in byte order check. It
also fixes 64-bit DWARF to read a 64-bit abbrev offset in the
compilation unit.
This is a backport of https://golang.org/cl/71171, which will be inthe
Go 1.10 release, to the gofrontend copy. Doing it now because AIX is
pretty much
On 10/20/2017 02:12 AM, Richard Biener wrote:
On Fri, Oct 20, 2017 at 4:03 AM, Sandra Loosemore
wrote:
This is the set of nios2 optimization patches that I've previously
mentioned in these threads:
https://gcc.gnu.org/ml/gcc/2017-10/msg00016.html
https://gcc.gnu.org/ml/gcc-patches/2017-10/msg0
We have a special 'as-base' instance of each class, for use in derived
layouts. for some classes this is just the regular class itself, but
for others it's a new instance. This instance is not in the
class-members, and that's now biting me on the modules branch (i'd been
punting on it before)
The recent SD-6 drafts define a macro for std::byte, so this patch
adds it.
* include/c_global/cstddef: Define __cpp_lib_byte feature-test macro.
* testsuite/18_support/byte/requirements.cc: Check macro.
Tested powerpc64le-linux, committed to trunk and gcc-7-branch.
commit 22d1
Hi,
On 10/20/2017 10:45 AM, Nathan Sidwell wrote:
On 10/20/2017 12:37 PM, Mukesh Kapoor wrote:
Hi,
This patch fixes https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80955.
Handle user-defined literals correctly in lex_string(). An empty
string followed by an identifier is
a valid user-defined li
On 10/20/2017 12:37 PM, Mukesh Kapoor wrote:
Hi,
This patch fixes https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80955.
Handle user-defined literals correctly in lex_string(). An empty string
followed by an identifier is
a valid user-defined literal. Don't issue a warning for this case.
a) why
Dear All,
The attached patch is pretty clear with the ChangeLogs and is very
nearly obvious.
Bootstrapped and regtested on FC23/x86_64 - OK for trunk?
Paul
2017-10-20 Paul Thomas
PR fortran/82586
* decl.c (gfc_get_pdt_instance): Remove the error message that
the parameter does n
The Posix method of calculating absolute deadlines is adopted in
favor of latching the monotonic clock to a known epoch, as the Posix
method is simpler and meets all the requirements of the Ada LRM.
Tested on x86_64-pc-linux-gnu, committed on trunk
2017-10-20 Doug Rupp
* libgnarl/s-os
This patch corrects an issue whereby a child package included into the body of
a parent forced checks on ineffective use clauses within the parent's spec to
be checked early - leading to spurious warnings.
-- Source --
-- pp.ads
package PP is
type Object is null reco
This patch fixes some spurious warnings and errors on dispatching calls to
synchronized operations when the controlling formal of the operation is an
access to interface type.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
2017-10-20 Ed Schonberg
* sem_util.adb (Is_Contro
Hi,
This patch fixes https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80955.
Handle user-defined literals correctly in lex_string(). An empty string
followed by an identifier is
a valid user-defined literal. Don't issue a warning for this case.
Bootstrapped and tested with 'make check' on x86_64-l
This patch corrects an issue whereby a defaulted formal package actual
generated a spurious type mismatch error upon instantiation instead of beging
accepted as per ARM 12.7 4.4/3.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
2017-10-20 Justin Squirek
* sem_ch12.adb (Ch
The new implementation of Access-Before-Elaboration detection can create new
raise Program_Error statements at the very end of the front-end processing,
which is too late in order for the first-line mechanism implementing the
No_Exception_Propagation restriction present in the front-end to catch th
Temporary entities created by the frontend are now marked as internal to
simplify their detection in the GNATprove backend. Also, by marking them
as internal it is less likely that an extra code for their initialization
will be created if pragma Initialize_Scalars is active (though I didn't
check t
Errors where previously silenced on expression functions, which caused
some BUG BOX to be issued inside GNATprove, as the AST could be
ill-formed. Now fixed. There is no example code as this only has an effect
on GNATprove.
Tested on x86_64-pc-linux-gnu, committed on trunk
2017-10-20 Yannick Moy
The dimension system in GNAT now allows to compare a dimensioned
expression with a literal, but it issues a warning in this case if the
literal is not zero.
The following code compiles with warnings:
$ gcc -c use_dims.adb
1. with System.Dim.Mks; use System.Dim.Mks;
2.
3. proc
On Wed, Oct 18, 2017 at 3:15 PM, Sam van Kampen via gcc-patches
wrote:
> On Wed, Oct 18, 2017 at 09:46:08AM -0600, Martin Sebor wrote:
>> > Fair enough, I didn't know whether to change the way it currently was
>> > triggered. Do you think it should fall under -Wextra (I don't think it
>> > falls u
On October 20, 2017 5:43:40 PM GMT+02:00, Martin Sebor wrote:
>On 10/20/2017 02:08 AM, Richard Biener wrote:
>> On Fri, Oct 20, 2017 at 1:00 AM, Martin Sebor
>wrote:
>>> On 10/19/2017 02:34 AM, Richard Biener wrote:
On Thu, Oct 19, 2017 at 1:19 AM, Martin Sebor
>wrote:
>
> On 1
On 10/20/2017 02:08 AM, Richard Biener wrote:
On Fri, Oct 20, 2017 at 1:00 AM, Martin Sebor wrote:
On 10/19/2017 02:34 AM, Richard Biener wrote:
On Thu, Oct 19, 2017 at 1:19 AM, Martin Sebor wrote:
On 10/18/2017 04:48 AM, Richard Biener wrote:
On Wed, Oct 18, 2017 at 5:34 AM, Martin Seb
If the dimensioned root type is an integer type, it is not particularly useful,
and fractional dimensions do not make much sense for such types, so previously
we used to reject dimensions of integer types that were not integer literals.
However, the manipulation of dimensions does not depend on the
The handling of string concatenation is quite inefficient in the front-end
because the compiler generates a lot of implicit concatenation operators for
array types and also enumeration types, and then walks the full list every
time it needs to resolve a concatenation operator, in most cases for str
On 13/10/17 08:41, Christophe Lyon wrote:
> Hi,
>
> The attached small patch solves PR 67591 and removes occurrences of
> "IT blocks containing 32-bit Thumb instructions are deprecated in
> ARMv8". It is similar to the patch I committed recently and updates
> the 3 remaining patterns that can gene
On 16/10/17 14:26, Dominik Inführ wrote:
> Hi,
>
> it seems the type attributes for neon_stp and neon_store1_1reg should be
> the other way around.
>
Yes, I agree, but there's more
Firstly, we have two patterns that are named *aarch64_simd_mov,
with different iterators. That's slightly co
This fixes another antic iteration issue. We were choosing a random
expression when intersecting ANTIC_OUT (that translated along the
first edge). This leads to oscillations if this expression changes
from iteration to iteration. The fix is to make sure we're picking
always the same expression
On 16/10/17 21:45, Christophe Lyon wrote:
> Hi,
>
> I have noticed a few testcases where dg-do should be moved as the
> first directive, and others where dg-options should be moved before
> dg-add-options. The attached patch does that. I noticed no difference
> in testing, at least because the arm
On 20/10/17 13:45, Alexandre Oliva wrote:
> On Oct 19, 2017, "Richard Earnshaw (lists)"
> wrote:
>
>> On 19/10/17 09:14, Richard Biener wrote:
>>> I guess Alex work on stmt frontiers will fix this instance?
>
>> Don't stmt frontiers just enable you to identify exactly one stopping
>> point with
From: Richard Biener
Sent: 20 October 2017 12:24
To: Bin Cheng
Cc: gcc-patches@gcc.gnu.org; nd
Subject: Re: [PATCH GCC][3/3]Refine CFG and bound information for split loops
On Thu, Oct 19, 2017 at 3:26 PM, Bin Cheng wrote:
> Hi,
> This is a rework of patch at
> https://gcc.gnu.org/m
Hello,
The following patch improves both the speed and code size for 64 bit
subtraction for RL78:
it emits a library function call instead of emitting code for the 64 bit add
for every single subtraction.
The subtraction function which was added in libgcc is hand written, so more
optimal than
On Oct 19, 2017, "Richard Earnshaw (lists)" wrote:
> On 19/10/17 09:14, Richard Biener wrote:
>> I guess Alex work on stmt frontiers will fix this instance?
> Don't stmt frontiers just enable you to identify exactly one stopping
> point with each statement, so that you don't keep repeatedly step
Libatomic builds a few functions for Arm with an explicit -march option.
This option does not specify an FPU, which can lead to problems when
targeting a hard-float or softfp environment since the architecture
appears to be incompatible with the selected ABI. This is some fallout
from the move to
On Fri, 20 Oct 2017, Uros Bizjak wrote:
> 2017-10-20 Uros Bizjak
>
> * config/i386/i386.c (ix86_fp_compare_mode): Return CCFPmode
> for ordered inequality comparisons even with TARGET_IEEE_FP.
This is PR target/52451.
A testcase (conditional on the fenv_exceptions effective-target) t
On Fri, Oct 20, 2017 at 1:34 PM, Richard Biener
wrote:
> On Fri, Oct 20, 2017 at 1:19 PM, Andreas Krebbel
> wrote:
>> On 10/20/2017 10:28 AM, Richard Biener wrote:
>>> On Fri, Oct 20, 2017 at 9:53 AM, Jakub Jelinek wrote:
On Fri, Oct 20, 2017 at 09:48:38AM +0200, Richard Biener wrote:
>
On Fri, Oct 20, 2017 at 1:19 PM, Andreas Krebbel
wrote:
> On 10/20/2017 10:28 AM, Richard Biener wrote:
>> On Fri, Oct 20, 2017 at 9:53 AM, Jakub Jelinek wrote:
>>> On Fri, Oct 20, 2017 at 09:48:38AM +0200, Richard Biener wrote:
How does it work semantically to have different exec charsets?
On Thu, Oct 19, 2017 at 3:26 PM, Bin Cheng wrote:
> Hi,
> This is a rework of patch at
> https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01037.html.
> The new patch doesn't try to handle all cases, instead, it only handles
> obvious cases.
> It also tries to add tests illustrating different cases
On 10/20/2017 10:28 AM, Richard Biener wrote:
> On Fri, Oct 20, 2017 at 9:53 AM, Jakub Jelinek wrote:
>> On Fri, Oct 20, 2017 at 09:48:38AM +0200, Richard Biener wrote:
>>> How does it work semantically to have different exec charsets? That is,
>>> if "strings" flow from a region with one -fexec-
The following fixes PR82473 - we were using a random (the first
non-reduction) operand of the reduction stmt to compute ncopies
but that's of course wrong.
Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
Richard.
2017-10-20 Richard Biener
PR tree-optimization/82473
Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
Richard.
2017-10-20 Richard Biener
PR tree-optimization/82473
* tree-if-conv.c (predicate_mem_writes): Make sure to only
remove false predicated stores.
* gcc.dg/torture/pr82603.c: New testcase.
This tames dumping a bit and adjusts whitespacing and order of dumping.
Bootstrapped / tested on x86_64-unknown-linux-gnu, applied.
Richard.
2017-10-20 Richard Biener
* graphite-isl-ast-to-gimple.c
(translate_isl_ast_to_gimple::graphite_copy_stmts_from_block):
Remove
Hi,
On 19 October 2017 at 13:17, Jakub Jelinek wrote:
> On Thu, Oct 19, 2017 at 02:07:24PM +0300, Maxim Ostapenko wrote:
>> > Is the patch (the merge + this incremental) ok for trunk?
>>
>> I think the patch is OK, just wondering about two things:
>
> Richi just approved the patch on IRC, so I'll
On Wed, Oct 4, 2017 at 9:39 PM, Jakub Jelinek wrote:
> Hi!
>
> While working on the previous patch, I've noticed we have quite a few
> seemingly useless isa attributes (first I've noticed isa attribute
> which had one value for all alternatives, which IMHO should just
> been done in insn condition
On 10/19/2017 10:49 AM, Bin.Cheng wrote:
On Thu, Oct 19, 2017 at 9:31 AM, Tom de Vries wrote:
On 10/09/2017 03:34 PM, Richard Biener wrote:
On Thu, Oct 5, 2017 at 3:16 PM, Bin Cheng wrote:
Hi,
Function generate_loops_for_partition chooses arbitrary path when
removing exit
condition not in
Hello!
Attached patch makes FP inequality comparisons trap on qNaN. There is
an old comment mentioned reversible comparisons, but middle end
doesn't reverse them anymore (a couple of weeks ago, reversed
comparisons were removed from i386.md):
/* ??? In order to make all comparisons reversible, we
Because of the recent reorganization of the ada/ directory, the check for the
presence of a working Ada compiler fails in stage #2 and later if you don't
have a compiler already installed in the --prefix directory.
Bootstrapped on x86_64-suse-linux, applied on the mainline.
2017-10-20 Nicolas
On Thu, Oct 19, 2017 at 08:03:45PM -0600, Sandra Loosemore wrote:
> A harder problem is that doing the high/lo_sum splitting in expand
> inhibits subsequent optimizations. One such problem arises when you
> have accesses to multiple fields in a static structure object. Expand
> sees this as many
On Fri, Oct 20, 2017 at 9:18 AM, Richard Biener
wrote:
> On Fri, Oct 20, 2017 at 10:12 AM, Richard Biener
>> How do other targets handle this situation? Naiively I'd have handled
>> the splitting at reload/LRA time ... (which would make the flag
>> to test reload_completed)
>>
>> There are quite
Hi,
This patch written by Olga Makhotina adds listed below missing intrinsics:
_mm512_[mask_]cmpeq_[pd|ps]_mask
_mm512_[mask_]cmple_[pd|ps]_mask
_mm512_[mask_]cmplt_[pd|ps]_mask
_mm512_[mask_]cmpneq_[pd|ps]_mask
_mm512_[mask_]cmpnle_[pd|ps]_mask
_mm512_[mask_]cmpnlt_[pd|ps]_mask
_mm512_[mask_]cmpo
On Fri, Oct 20, 2017 at 9:53 AM, Jakub Jelinek wrote:
> On Fri, Oct 20, 2017 at 09:48:38AM +0200, Richard Biener wrote:
>> How does it work semantically to have different exec charsets? That is,
>> if "strings" flow from a region with one -fexec-charset setting to a region
>> with another one is
On Fri, Oct 20, 2017 at 4:09 AM, Sandra Loosemore
wrote:
> This patch adds a function to indicate whether the split1 pass has run
> yet. This is used in part 3 of the patch set to decide whether 32-bit
> symbolic constant expressions are permitted, e.g. in
> TARGET_LEGITIMATE_ADDRESS_P and the mo
I can't propose general solution since TARGET_PREFER256 is AVX512 specific.
Sorry for misunderstanding.
Sergey
-Original Message-
From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-ow...@gcc.gnu.org] On
Behalf Of Kirill Yukhin
Sent: Wednesday, October 18, 2017 8:10 PM
To: Shalnov, Se
On Dez 13 2015, Jeff Law wrote:
> diff --git a/gcc/config/m68k/m68k.md b/gcc/config/m68k/m68k.md
> index 1eaf58f..444515a 100644
> --- a/gcc/config/m68k/m68k.md
> +++ b/gcc/config/m68k/m68k.md
> @@ -7601,3 +7601,36 @@
>
> (include "cf.md")
> (include "sync.md")
> +
> +;; Convert
> +;;
> +;;
On Fri, Oct 20, 2017 at 10:12 AM, Richard Biener
wrote:
> On Fri, Oct 20, 2017 at 4:03 AM, Sandra Loosemore
> wrote:
>> This is the set of nios2 optimization patches that I've previously
>> mentioned in these threads:
>>
>> https://gcc.gnu.org/ml/gcc/2017-10/msg00016.html
>> https://gcc.gnu.org/m
On Fri, Oct 20, 2017 at 4:03 AM, Sandra Loosemore
wrote:
> This is the set of nios2 optimization patches that I've previously
> mentioned in these threads:
>
> https://gcc.gnu.org/ml/gcc/2017-10/msg00016.html
> https://gcc.gnu.org/ml/gcc-patches/2017-10/msg00957.html
>
> To give an overview of wha
On Fri, Oct 20, 2017 at 1:00 AM, Martin Sebor wrote:
> On 10/19/2017 02:34 AM, Richard Biener wrote:
>>
>> On Thu, Oct 19, 2017 at 1:19 AM, Martin Sebor wrote:
>>>
>>> On 10/18/2017 04:48 AM, Richard Biener wrote:
On Wed, Oct 18, 2017 at 5:34 AM, Martin Sebor wrote:
>
>
>>
On Fri, Oct 20, 2017 at 09:48:38AM +0200, Richard Biener wrote:
> How does it work semantically to have different exec charsets? That is,
> if "strings" flow from a region with one -fexec-charset setting to a region
> with another one is that undefined behavior? Do we now require
> external funct
On Thu, Oct 19, 2017 at 7:13 PM, Martin Sebor wrote:
> On 10/19/2017 09:50 AM, Andreas Krebbel wrote:
>>
>> The TPF operating system uses the GCC S/390 backend. They set an
>> EBCDIC exec charset for compilation using -fexec-charset. However,
>> certain libraries require ASCII strings instead.
74 matches
Mail list logo
