On 10/09/2018 01:31 PM, Jonathan Wakely wrote:
On 09/10/18 07:25 +0200, François Dumont wrote:
As we talked one day I would like to make all iterator operators
global for consistency. So here is the patch to do so for std::list
iterators.
By "global" you mean "non-member", right?
Yes,
On Oct 10, 2018, JonY <10wa...@gmail.com> wrote:
> On 10/10/2018 03:24 AM, Alexandre Oliva wrote:
>> On Oct 9, 2018, JonY <10wa...@gmail.com> wrote:
>> Now, if you wish it to affect Cygwin as well, I could implement that,
>> and drop -mingw from the option name. I'd retain the current defaults
On 10/10/2018 03:24 AM, Alexandre Oliva wrote:
> On Oct 9, 2018, JonY <10wa...@gmail.com> wrote:
>
>> It is fine to turn it on by default in 32bit MinGW (i686-*-mingw*), but
>> leave the defaults as is for others like Cygwin, I am not too sure of
>> the effects for Cygwin.
>
> Cygwin already
On Oct 9, 2018, JonY <10wa...@gmail.com> wrote:
> It is fine to turn it on by default in 32bit MinGW (i686-*-mingw*), but
> leave the defaults as is for others like Cygwin, I am not too sure of
> the effects for Cygwin.
Cygwin already has --large-address-aware enabled, without an option to
This patch renames the "error" callback within libcpp
to "diagnostic", and uses the pair of enums in cpplib.h, rather
than passing two different kinds of "int" around.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Committed to trunk as r264999.
gcc/c-family/ChangeLog:
*
Fixed all issues pointed in the previous iteration.
There is now a significant change regarding how the sin(atan(x))
constant is calculated, as now it checks for which values such that
computing 1 + x*x won't overflow. There are two reasons for this
change: (1) Avoid an intermediate infinity value
On 10/08/2018 03:36 PM, Peter Bergner wrote:
PR87507 shows a problem where IRA assigns a non-volatile TImode reg pair to
a pseudo when there is a volatile reg pair available to use. This then
causes us to emit save/restore code for the non-volatile reg usage.
The problem here is that the only
On Tue, Oct 9, 2018 at 1:19 PM David Malcolm wrote:
> + /* Emulation of a "move" constructor, but really a copy
> + constructor. */
> +
> + name_hint (const name_hint )
> + : m_suggestion (other.m_suggestion),
> +m_deferred (const_cast (other).take_deferred ())
> + {
> + }
> +
> +
On Tue, Oct 09 2018, Martin Liška wrote:
> Hi.
>
> Utilizing rtags' --find-dead-functions I'm suggesting a removal of part
> of the functions reported with the script. I built all cross compilers
> defined in contrib/config-list.mk and I fixed VMS targets that I broke
> in previous removal.
>
> If
* Jeff Law:
> On 03/29/2018 08:00 AM, Florian Weimer wrote:
>> This patch performs lazy initialization of the relevant CPUID feature
>> register value. It will needlessly invoke the CPUID determination code
>> on architectures which lack CPUID support or support for the feature
>> register, but
OK.
On Tue, Oct 9, 2018 at 1:49 PM Paolo Carlini wrote:
>
> Hi,
>
> On 09/10/18 17:17, Jason Merrill wrote:
> > On Sat, Sep 29, 2018 at 3:27 PM Paolo Carlini
> > wrote:
> >> Hi again,
> >>
> >> On 9/28/18 9:15 PM, Paolo Carlini wrote:
> >>> Thanks. About the location, you are certainly right,
Hi,
On 09/10/18 17:17, Jason Merrill wrote:
On Sat, Sep 29, 2018 at 3:27 PM Paolo Carlini wrote:
Hi again,
On 9/28/18 9:15 PM, Paolo Carlini wrote:
Thanks. About the location, you are certainly right, but doesn't seem
trivial. Something we can do *now* is using
In the C++ FE, after emitting various errors about unrecognized names,
the parser can call
suggest_alternatives_for
and/or
suggest_alternative_in_explicit_scope.
These can issue zero or more suggestions for the unrecognized name,
or various other "note" diagnostics suggesting how to fix the
> 2018-09-28 Eric Botcazou
>
> PR tree-optimization/86659
> * gimple-match.h (struct gimple_match_op): Add reverse field.
Jonathan privately remarked that the new member should probably be initialized
in the constructors (thanks!). Done thusly, applied on mainline as obvious.
> Which version exactly (pkg list entire) of Solaris 11 are you running?
> I'm using gas 2.31 and /bin/ld on Solaris 11.4 resp. 11.5 Beta, where
> Bernd's patch in PR bootstrap/87551 fixed the remaining regressions.
Solaris 11.3 with Gas 2.30.
--
Eric Botcazou
This patch by Cherry Zhang skips the testSetPanicOnFault tests when
using gollvm. LLVM doesn't support non-call exceptions. This test was
passing more or less by luck: if the faulting instruction is between
two calls with the same landing pad (in instruction layout order, not
the program's logic
On Sat, Sep 29, 2018 at 3:27 PM Paolo Carlini wrote:
> Hi again,
>
> On 9/28/18 9:15 PM, Paolo Carlini wrote:
> > Thanks. About the location, you are certainly right, but doesn't seem
> > trivial. Something we can do *now* is using
> > declspecs->locations[ds_typedef] and
This change is aimed at getting rid of spurious -Wuninitialized warnings
issued for small records passed by copy and containing default values
for some of their components.
The source of the problem is that the _Init parameter of the
initialization routine is declared as an in/out parameter, so
GNATprove does not have sometimes the precise information of the
compiler about size of types and objects, so that it cannot evaluate the
expressions in pragma Compile_Time_Error/Warning the same way the
compiler does. Thus, these pragmas should be ignored in GNATprove mode,
as it can neither
This fixlet gets rid of a spurious error issued in the specific case of
a call to a subprogram taking an Out parameter of a discriminated record
type without default discriminants, if the actual parameter is the
result of the conversion to the record type of a variable whose type is
derived from
The back-end was recently changed to issue more -Wuninitialized warnings
on Out parameters and this has caught a case related to
Ada.Iterator_Interface.: This patchlet simply kills this uninteresting
warning.
Tested on x86_64-pc-linux-gnu, committed on trunk
2018-10-09 Eric Botcazou
gcc/ada/
This fixes a recent regression introduced in the compiler for the
inlined renaming of a subprogram instantiated in a package body. It was
wrongly clearing the Is_Public flag on the entity associated with the
body.
Tested on x86_64-pc-linux-gnu, committed on trunk
2018-10-09 Eric Botcazou
This patch removes an improper error message on a visibility change in
an aspect expression between the freeze point and the end of the
declaration list, when the expression involves a call to a instance of
Unchecked_Conversion and the enclosing package declaration has a package
body with multiple
On Tue, Oct 9, 2018 at 3:28 PM Richard Biener wrote:
>
> On Mon, 8 Oct 2018, Richard Biener wrote:
>
> > On Fri, 5 Oct 2018, Uros Bizjak wrote:
> >
> > > On Thu, Oct 4, 2018 at 2:05 PM Richard Biener wrote:
> > > >
> > > >
> > > > This tries to apply the same trick to sminmax reduction patterns
On Mon, 2018-09-24 at 10:56 -0600, Martin Sebor wrote:
> On 09/21/2018 04:09 PM, David Malcolm wrote:
> > This is v2 of the patch; I managed to bit-rot my own patch due to
> > my
> > fix for r264335, which tightened up the "is this meaningful"
> > threshold
> > on edit distances when finding
On Mon, 8 Oct 2018, Richard Biener wrote:
> On Fri, 5 Oct 2018, Uros Bizjak wrote:
>
> > On Thu, Oct 4, 2018 at 2:05 PM Richard Biener wrote:
> > >
> > >
> > > This tries to apply the same trick to sminmax reduction patterns
> > > as for the reduc_plus_scal ones, namely reduce %zmm -> %ymm ->
Hi!
As the following testcase additions show, even the TYPE_MAX_VALUE var needs
to be forced into temporary if it is a user variable, otherwise if that
variable is changed by the user before taskgroup ends, we don't handle it
correctly.
In addition to that, this patch removes useless NULL second
The typedefs for common specializations of std::__cxx11::basic_string do
not need to be in the std::__cxx11 namespace. Those typedefs are never
used for linkage purposes so don't appear in mangled names, and so don't
need to be distinct from the equivalent typedefs for the COW
std::basic_string
Hi Bernd,
>> * The merge-all-constants-2.c test doesn't FAIL on Solaris/SPARC with
>>/bin/as, although it lacks string merging support, too. The assembler
>>output contains
>>
>> .section".rodata"
>>
>>so the pattern currently used to check for .rodata is too
>>
On 10/03/18 18:31, Jeff Law wrote:
>> - && (len = int_size_in_bytes (TREE_TYPE (decl))) > 0
>> - && TREE_STRING_LENGTH (decl) >= len)
>> + && (len = int_size_in_bytes (TREE_TYPE (decl))) >= 0
>> + && TREE_STRING_LENGTH (decl) == len)
> Not sure why you want to test for >= 0
Hi Richard,
> -Original Message-
> From: Richard Biener
> Sent: Tuesday, October 9, 2018 08:28
> To: Tamar Christina
> Cc: Jeff Law ; gcc-patches@gcc.gnu.org; nd
> ; i...@airs.com
> Subject: RE: [PATCH][GCC][mid-end] Add a hook to support telling the mid-
> end when to probe the stack
Hi.
In non-LTO mode, we should not set hotness according to computed histogram
in ipa-profile. Following patch does that and fixes the test-case isolated
from PR.
Patch survives regression tests on x86_64-linux-gnu.
Ready for trunk?
Thanks,
Martin
gcc/ChangeLog:
2018-10-09 Martin Liska
Hi Eric,
>> Besides, the patch seems to have produced more fallout on Solaris: I see
>> many new Go testsuite failures on Solaris 10 which probably are related,
>> and Solaris bootstrap with Ada included is broken due to the extended
>> usage of string merging. I'm currently investigating what's
This helps us throw away constraints from uninitialized stuff earlier.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2018-10-09 Richard Biener
PR tree-optimization/63155
* tree-ssa-structalias.c: Include tree-ssa.h.
On 10/9/18 11:03 AM, Rainer Orth wrote:
> Hi Martin,
>
>> rename from gcc/testsuite/g++.dg/ext/pr82625.C
>> rename to gcc/testsuite/g++.target/i386/pr82625.C
>> index 59b174f8c51..0eb70baed5e 100644
>> --- a/gcc/testsuite/g++.dg/ext/pr82625.C
>> +++ b/gcc/testsuite/g++.target/i386/pr82625.C
>> @@
Committed as obvious.
Richard.
2018-10-09 Richard Biener
* tree-vectorizer.c (dump_stmt_cost): Fix cut missing
replacements.
diff --git a/gcc/tree-vectorizer.c b/gcc/tree-vectorizer.c
index 0ab366b79a3..60ee7f6380c 100644
--- a/gcc/tree-vectorizer.c
+++
On 09/10/18 07:25 +0200, François Dumont wrote:
As we talked one day I would like to make all iterator operators
global for consistency. So here is the patch to do so for std::list
iterators.
By "global" you mean "non-member", right?
Thanks to this change the operators ==(iterator,
Hi,
gently pinging the below...
On 29/09/18 21:27, Paolo Carlini wrote:
Hi again,
On 9/28/18 9:15 PM, Paolo Carlini wrote:
Thanks. About the location, you are certainly right, but doesn't seem
trivial. Something we can do *now* is using
declspecs->locations[ds_typedef] and
On 10/09/2018 04:59 AM, Alexandre Oliva wrote:
> On Oct 5, 2018, Joseph Myers wrote:
>
>> A new configure option needs documenting in install.texi.
>
> Ah, yes, thanks for the reminder.
>
> On Oct 6, 2018, JonY <10wa...@gmail.com> wrote:
>
>> They're both OK as far as I can see. I just
Hi Martin,
> rename from gcc/testsuite/g++.dg/ext/pr82625.C
> rename to gcc/testsuite/g++.target/i386/pr82625.C
> index 59b174f8c51..0eb70baed5e 100644
> --- a/gcc/testsuite/g++.dg/ext/pr82625.C
> +++ b/gcc/testsuite/g++.target/i386/pr82625.C
> @@ -1,7 +1,7 @@
> /* { dg-do compile } */
> /* {
Hi.
There's another move of C++ tests, this time these that have dg-require-ifunc.
Key question is whether we want to make subfolders for i386 tests (ext, other,
..)?
Survives make check -k RUNTESTFLAGS="i386.exp"
Martin
>From d36db4d5b8306dcbe2d63762bc8596e05132e46a Mon Sep 17 00:00:00 2001
On 09/10/2018 09:27, Mihail Ionescu wrote:
> Hi all,
>
> This patch removes some of the machine mode checks from the arm backend when
> emitting instructions by using the '@' construct (Parameterized Names[2]). It
> is based on the previous AArch64 patch[1].
>
>
PING^1
On 9/26/18 11:33 AM, Martin Liška wrote:
> On 9/25/18 5:53 PM, Jakub Jelinek wrote:
>> On Tue, Sep 25, 2018 at 05:26:44PM +0200, Martin Liška wrote:
>>> The only missing piece is how to implement asan_emit_redzone_payload more
>>> smart.
>>> It means doing memory stores with 8,4,2,1 sizes
On Thu, Sep 27, 2018 at 10:55:10AM +0200, Martin Liška wrote:
> @@ -1281,15 +1284,30 @@ asan_emit_stack_protection (rtx base, rtx pbase,
> unsigned int alignb,
>pp_space (_pp);
>pp_wide_integer (_pp, offsets[l - 1] - offsets[l]);
>pp_space (_pp);
> +
> +
Hi.
Utilizing rtags' --find-dead-functions I'm suggesting a removal of part
of the functions reported with the script. I built all cross compilers
defined in contrib/config-list.mk and I fixed VMS targets that I broke
in previous removal.
If the folks are happy with the removal, I can probably
PING^1
On 9/27/18 10:55 AM, Martin Liška wrote:
> Hi.
>
> I've noticed ASAN can inform user about location of stack variables
> when a stack violation is detected.
>
> Sample example:
>
> ...
> This frame has 3 object(s):
> [32, 36) 'counter' (line 3) <== Memory access at offset 36
On Tue, 9 Oct 2018, Tamar Christina wrote:
> Hi All,
>
> I'm looking for permission to backport this patch to the GCC-8 branch
> to fix PR86486.
>
> OK for backport?
This doesn't seem to fix a regression and it's been on trunk only
for a few days.
Richard.
> Thanks,
> Tamar
>
> >
Hi All,
I'm looking for permission to backport this patch to the GCC-8 branch
to fix PR86486.
OK for backport?
Thanks,
Tamar
> -Original Message-
> From: Jeff Law
> Sent: Friday, August 3, 2018 19:03
> To: Tamar Christina ; Joseph Myers
>
> Cc: gcc-patches@gcc.gnu.org; nd ;
Hi All,
I'm looking for permission to backport this patch to the GCC-8 branch
to fix PR86486.
OK for backport?
Thanks,
Tamar
> -Original Message-
> From: gcc-patches-ow...@gcc.gnu.org
> On Behalf Of Tamar Christina
> Sent: Friday, September 28, 2018 17:36
> To: Jeff Law ;
Hi All,
I'm looking for permission to backport this patch to the GCC-8 branch
to fix PR86486.
OK for backport?
Thanks,
Tamar
> -Original Message-
> From: James Greenhalgh
> Sent: Tuesday, July 31, 2018 22:02
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
>
Hi All,
I'm looking for permission to backport this patch to the GCC-8 branch
to fix PR86486.
OK for backport?
Thanks,
Tamar
> -Original Message-
> From: Jeff Law
> Sent: Wednesday, July 11, 2018 19:53
> To: Tamar Christina ; gcc-patches@gcc.gnu.org
> Cc: nd ; rguent...@suse.de;
Hi All,
I'm looking for permission to backport this patch to the GCC-8 branch
to fix PR86486.
OK for backport?
Thanks,
Tamar
> -Original Message-
> From: gcc-patches-ow...@gcc.gnu.org
> On Behalf Of Tamar Christina
> Sent: Wednesday, September 26, 2018 09:30
> To:
Hi All,
I'm looking for permission to backport this patch to the GCC-8 branch
to fix PR86486.
OK for backport?
Thanks,
Tamar
> -Original Message-
> From: James Greenhalgh
> Sent: Tuesday, August 7, 2018 17:18
> To: Tamar Christina
> Cc: Jeff Law ; gcc-patches@gcc.gnu.org; nd
> ;
Hi All,
I'm looking for permission to backport this patch to the GCC-8 branch
to fix PR86486.
OK for backport?
Thanks,
Tamar
> -Original Message-
> From: James Greenhalgh
> Sent: Tuesday, September 11, 2018 16:56
> To: Tamar Christina
> Cc: Richard Sandiford ; Jeff Law
> ;
Hi All,
I'm looking for permission to backport this patch to the GCC-8 branch
to fix PR86486.
OK for backport?
Thanks,
Tamar
> -Original Message-
> From: Richard Sandiford
> Sent: Friday, September 28, 2018 18:18
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; James
55 matches
Mail list logo
