Hi,
On 25/04/19 23:14, Jason Merrill wrote:
On Tue, Apr 23, 2019 at 11:26 AM Paolo Carlini wrote:
I tried a few different things to avoid this simple error-recovery
regression but, all in all, I think it makes sense to simply bail out
early from grokdeclarator upon the first error. Tested
PR libstdc++/90252
* testsuite/lib/libstdc++.exp (check_effective_target_tbb-backend):
Changed v3_target_compile check from preprocess to executable.
---
libstdc++-v3/testsuite/lib/libstdc++.exp | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git
On 25/04/19 17:02 -0400, Jason Merrill wrote:
Perhaps initialize show_notes to (complain & tf_error), so you only
need to update it from permerror.
But doesn't fix the bug, because the error is only printed for
!is_instantiation_of_constexpr (current_function_decl)
so we need to suppress the
PR libstdc++/90239
* doc/xml/manual/status_cxx2020.xml: Amend P0591R4 status.
* include/std/scoped_allocator [__cplusplus > 201703L]
(scoped_allocator_adaptor::construct): Define in terms of
uses_allocator_construction_args, as per P0591R4.
*
On Thu, Apr 25, 2019 at 10:31:36PM +0100, Jonathan Wakely wrote:
> PR libstdc++/90239
> * doc/xml/manual/status_cxx2020.xml: Correct status of P0591R4.
> * doc/html/*: Regenerate.
>
> This corrects the docs to reflect the real status in gcc-9-branch.
> I'll fix it properly on
PR libstdc++/90239
* doc/xml/manual/status_cxx2020.xml: Correct status of P0591R4.
* doc/html/*: Regenerate.
This corrects the docs to reflect the real status in gcc-9-branch.
I'll fix it properly on trunk (and later backport it to 9.2).
commit
On Tue, Apr 23, 2019 at 11:26 AM Paolo Carlini wrote:
>
> I tried a few different things to avoid this simple error-recovery
> regression but, all in all, I think it makes sense to simply bail out
> early from grokdeclarator upon the first error. Tested x86_64-linux.
"type = error_mark_node"
OK.
On Thu, Apr 25, 2019 at 7:27 AM Jakub Jelinek wrote:
>
> On Thu, Apr 25, 2019 at 01:09:00PM +0200, Rainer Orth wrote:
> > > cp/
> > > * call.c (null_ptr_cst_p): Order checks according to expensiveness.
> > > (conversion_null_warnings): Likewise.
> > > * typeck.c
Perhaps initialize show_notes to (complain & tf_error), so you only
need to update it from permerror.
On Thu, Apr 25, 2019 at 4:31 PM Jonathan Wakely wrote:
>
> gcc/cp:
>
> PR c++/90243 - orphaned note in uninstantiated constexpr function
> * decl.c
gcc/cp:
PR c++/90243 - orphaned note in uninstantiated constexpr function
* decl.c (check_for_uninitialized_const_var): Suppress notes if no
error was shown.
gcc/testsuite:
PR c++/90243
* g++.dg/diagnostic/pr90243.C: New test.
Tested powerpc64le-linux,
On Thu, Apr 25, 2019 at 03:56:40PM -0400, Jason Merrill wrote:
> On Wed, Apr 24, 2019 at 5:26 PM Marek Polacek wrote:
> >
> > This valid test started to be accepted with r265789, which removed the
> > following checks.
>
> It didn't remove them, it moved them into invalid_tparm_referent_p.
> And
On 18.03.19 22:28, Andreas Tobler wrote:
On 18.03.19 22:22, Jeff Law wrote:
On 3/17/19 2:40 PM, Andreas Tobler wrote:
Hi all,
this patch adds support for multilib on x86_64-unknown-freebsd*
The multilibs are 32-bit.
This patch is functionality tested on gcc8 and gcc9. Test suite testing
is a
On Wed, Apr 24, 2019 at 5:26 PM Marek Polacek wrote:
>
> This valid test started to be accepted with r265789, which removed the
> following checks.
It didn't remove them, it moved them into invalid_tparm_referent_p.
And changed the tests for C++17.
> I wonder if we want to remove them in gcc 8,
2019-04-25 Uroš Bizjak
* doc/extend.texi (vector_size): Add missing comma after @xref.
Bootstrapped on x86_64-linux-gnu, committed to mainline SVN.
Uros.
Index: extend.texi
===
--- extend.texi (revision 270583)
+++
On Thu, Apr 25, 2019 at 11:02:09AM -0500, Kelvin Nilsen wrote:
> The attached patch resolves the issue described in this problem report. The
> patch has been bootstrapped and tested without regressions on
> powerpc64le-unknown-linux-gnu (both P8 and P9) and on powerpc64-linux (P7 and
> P8,
On 25/04/19 11:51 -0700, Thomas Rodgers wrote:
Revised patch.
From 074685cf74b48604244c0c6f1d8cba63ff8915e5 Mon Sep 17 00:00:00 2001
From: Thomas Rodgers
Date: Wed, 24 Apr 2019 15:53:45 -0700
Subject: [PATCH] Implement LWG 3062, Unnecessary decay_t in
is_execution_policy_v
should
Revised patch.
>From 074685cf74b48604244c0c6f1d8cba63ff8915e5 Mon Sep 17 00:00:00 2001
From: Thomas Rodgers
Date: Wed, 24 Apr 2019 15:53:45 -0700
Subject: [PATCH] Implement LWG 3062, Unnecessary decay_t in
is_execution_policy_v
should be remove_cvref_t
* include/pstl/execution_defs.h
On Thu, Apr 25, 2019 at 04:58:57PM +0200, Richard Biener wrote:
> 2019-04-25 Richard Biener
>
> PR middle-end/89765
> * gimplify.c (gimplify_expr): Avoid turning a lvalue
> VIEW_CONVERT_EXPR into one operating on an rvalue.
Successfully bootstrapped/regtested on
By using ASM_OUTPUT_LABEL, r257511 forced the assembler to start a new
bundle when emitting an inline entry label on. Instead, use
ASM_OUTPUT_DEBUG_LABEL like for the block begin and end labels so tags are
emitted rather than labels.
gcc/
PR bootstrap/87338
* dwarf2out.c
There's a linter in contrib/check-internal-format-escaping.py that
checks whether the base file for translations (such as French or German)
conform to some basic style rules. This mostly affects the diagnostics
emitted by GCC.
As the German translation I have added several checks to the linter
I'm pinging this patch as it's old now and should be applied to fix the bug.
Nick
On 2019-04-08 7:20 p.m., Nicholas Krause wrote:
> This fixes the caller in tsubst_requires_expr to
> tsubst_constraint_variables to wrap their respective
> trees in PARM_CONSTR_PARMS. This is to get the correct
>
On Thu, Apr 25, 2019 at 1:03 AM Uros Bizjak wrote:
>
>
>
> On Thu, Apr 25, 2019 at 9:51 AM Martin Liška wrote:
>>
>> On 4/23/19 10:29 AM, Martin Liška wrote:
>> > On 4/18/19 7:44 PM, H.J. Lu wrote:
>> >> On Thu, Apr 18, 2019 at 4:07 AM Martin Liška wrote:
>> >>>
>> >>> Hi.
>> >>>
>> >>> I'm
The attached patch resolves the issue described in this problem report. The
patch has been bootstrapped and tested without regressions on
powerpc64le-unknown-linux-gnu (both P8 and P9) and on
powerpc64-unknown-linux-gnu (P7 and P8, both -m32 and -m64).
Is this ok for trunk and backports?
On 25/04/2019 16:45, Jakub Jelinek wrote:
> On Thu, Apr 25, 2019 at 03:32:41PM +0100, Richard Earnshaw (lists) wrote:
>>> --- a/libphobos/libdruntime/core/sys/posix/sys/stat.d
>>> +++ b/libphobos/libdruntime/core/sys/posix/sys/stat.d
>>> @@ -709,10 +709,10 @@ version (CRuntime_Glibc)
>>>
The attached patch resolves the issue described in this problem report. The
patch has been bootstrapped and tested without regressions on
powerpc64le-unknown-linux-gnu (both P8 and P9) and on powerpc64-linux (P7 and
P8, both -m32 and -m64).
Is this ok for trunk and backports?
Thanks.
Hi,
Patch fixes a tlsgc bug on non-glibc targets.
As explained in the bug report, glibc puts the TLS area for each new
thread at the beginning of the newly created stack. Due to the way
libdruntime detects the stack bottom, we end up marking all TLS data
along with what we think is the stack.
On Thu, Apr 25, 2019 at 03:32:41PM +0100, Richard Earnshaw (lists) wrote:
> > --- a/libphobos/libdruntime/core/sys/posix/sys/stat.d
> > +++ b/libphobos/libdruntime/core/sys/posix/sys/stat.d
> > @@ -709,10 +709,10 @@ version (CRuntime_Glibc)
> > }
> > int[2] __unused;
> >
I merged trunk revision 270573 to the gccgo branch.
Ian
On Thu, Apr 25, 2019 at 4:46 PM Jeff Law wrote:
>
>
> In the discussion for pr90037 Richi noticed that we had a cprop pass
> after the restrict warning pass. Those should be swapped. This patch
> swaps them.
>
> Bootstrapped and regression tested on x86_64.
>
> I wouldn't lose sleep if we
This fixes the ICE seen by the ppc testcase in the PR. The gimplifier
was blindly turning a VIEW_CONVERT_EXPR into an rvalue even if that
isn't allowed.
Bootstrap / regtest running on x86_64-unknown-linux-gnu, OK?
Can ppc folks add the testcase (maybe once they figure out the
remaining
In the discussion for pr90037 Richi noticed that we had a cprop pass
after the restrict warning pass. Those should be swapped. This patch
swaps them.
Bootstrapped and regression tested on x86_64.
I wouldn't lose sleep if we decided to defer this to gcc-10. But given
Richi and I both think
On Thu, 25 Apr 2019 at 16:32, Richard Earnshaw (lists)
wrote:
>
> On 24/04/2019 12:10, Iain Buclaw wrote:
> > On Wed, 24 Apr 2019 at 09:33, Andreas Schwab wrote:
> >>
> >> On Apr 24 2019, Iain Buclaw wrote:
> >>
> >>> This patch adds arch64*-*-linux* as a supported libphobos target,
> >>>
Committed as obvious.
Richard.
2019-04-25 Richard Biener
* tree-pass.h (make_pass_phi_only_cprop): Remove.
* timevar.def (TV_TREE_PHI_CPROP): Likewise.
Index: gcc/tree-pass.h
===
--- gcc/tree-pass.h
On 24/04/2019 12:10, Iain Buclaw wrote:
> On Wed, 24 Apr 2019 at 09:33, Andreas Schwab wrote:
>>
>> On Apr 24 2019, Iain Buclaw wrote:
>>
>>> This patch adds arch64*-*-linux* as a supported libphobos target,
>>> something that has been passing the testsuite for a while now.
>>>
>>> Committed to
Hi!
On Fri, 5 Oct 2018 21:03:36 +0100, Julian Brown wrote:
> Continuing the thread from here:
>
> https://gcc.gnu.org/ml/gcc-patches/2016-02/msg00198.html
>
> On Wed, 3 Feb 2016 19:52:09 +0300
> Alexander Monakov wrote:
>
> > On Wed, 3 Feb 2016, Nathan Sidwell wrote:
> > > You can only
On Wed, Apr 24, 2019 at 12:16:39PM -0600, Jeff Law wrote:
> On 4/24/19 7:05 AM, Segher Boessenkool wrote:
> > On Mon, Apr 22, 2019 at 09:09:12AM -0600, Jeff Law wrote:
> >> First, it re-uses combine's make_field_assignment in the aarch64
> >> backend.
> >
> > That's not really acceptable.
os testing, as noticed during a
i386-pc-solaris2.11 build. All link tests FAIL like this:
FAIL: libphobos.cycles/mod1.d --DRT-oncycle=print (test for excess errors)
Excess errors:
Undefined first referenced
symbol in file
fiber_switchContext
Hi Kewen,
Cool stuff.
On Wed, Apr 24, 2019 at 04:41:01PM +0800, Kewen.Lin wrote:
> One failure was found in regression testing, which is:
> gcc.target/powerpc/20050830-1.c
>
> I did some investigation and found: with this patch, one new iv cand
> is chosen for exit condition, which is used to
On Thu, 25 Apr 2019, Jakub Jelinek wrote:
> On Thu, Apr 25, 2019 at 01:39:02PM +0200, Richard Biener wrote:
> > > Regtested on x86_64-linux and i686-linux, ok for trunk?
> >
> > The patch would be obvious but I wonder how the above can change
> > anything... (but I can reproduce with even only
On Thu, Apr 25, 2019 at 01:39:02PM +0200, Richard Biener wrote:
> > Regtested on x86_64-linux and i686-linux, ok for trunk?
>
> The patch would be obvious but I wonder how the above can change
> anything... (but I can reproduce with even only that change)
Haven't stepped through it in a
On Thu, 25 Apr 2019, Jakub Jelinek wrote:
> On Thu, Apr 25, 2019 at 01:09:00PM +0200, Rainer Orth wrote:
> > > cp/
> > > * call.c (null_ptr_cst_p): Order checks according to expensiveness.
> > > (conversion_null_warnings): Likewise.
> > > * typeck.c
Am 25.04.19 um 12:57 schrieb Iain Buclaw:
Originally reviewed and tested here:
https://github.com/D-Programming-GDC/gcc/pull/11
OK, but for want of a better way to do this. However I think its
right to have better support for targets without libphobos.
I've attached a couple knit changes.
On Thu, Apr 25, 2019 at 01:09:00PM +0200, Rainer Orth wrote:
> > cp/
> > * call.c (null_ptr_cst_p): Order checks according to expensiveness.
> > (conversion_null_warnings): Likewise.
> > * typeck.c (same_type_ignoring_top_level_qualifiers_p): Return
> > early if type1 == type2.
Hi Richard,
> On Tue, 16 Apr 2019, Richard Biener wrote:
>
>>
>> Two cases from a -fsynax-only tramp3d callgrind profile.
>
> Amended by two others.
>
> Bootstrapped and tested on x86_64-unknown-linux-gnu.
>
> OK?
>
> Thanks,
> Richard.
>
> 2019-04-17 Richard Biener
>
> cp/
> *
On Thu, 25 Apr 2019 at 12:25, Johannes Pfau wrote:
>
> This adds emulated TLS support to druntime.
> The main problem here is that the D garbage collector needs
> to be able to scan the TLS memory for pointers, which is not
> possible with the current libgcc implementation.
>
> This therefore
On Sun, 14 Apr 2019 at 18:40, Johannes Pfau wrote:
>
> Even if we disable libphobos (as unsupported in libphobos/configure.tgt
> or using --disable-libphobos), config-lang.in still adds target-libbacktrace
> to the target_libs. This means target-zlib and target-libbacktrace still end
> up
>
Hi!
On Wed, 11 Oct 2017 07:31:04 -0700, Cesar Philippidis
wrote:
> I've pushed this patch to openacc-gcc-7-branch which teaches the
> gimplifier how to create 0-length arrays mappings for certain pointer
> and reference typed variables. This is necessary to satisfy the implicit
> expectation in
On Thu, Apr 25, 2019 at 12:04:24PM +0200, Richard Biener wrote:
> >Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
>
> So if you put a breakpoint on the for line is the behavior after the patch
> now the same as before stmt frontiers if you do 'continue' repeatedly?
The cc1
This adds emulated TLS support to druntime.
The main problem here is that the D garbage collector needs
to be able to scan the TLS memory for pointers, which is not
possible with the current libgcc implementation.
This therefore reimplements the libgcc emutls
support (__emutls_get_address, ...)
On April 25, 2019 11:13:34 AM GMT+02:00, Jakub Jelinek wrote:
>Hi!
>
>The introduction of -gstatement-frontiers (and making it the default)
>regressed debug info experience on the attached testcases (not
>including
>in the testsuite, as not sure how to model that in the guality
>testsuite).
>The
On Wed, 24 Apr 2019 at 15:28, Kamil Rytarowski wrote:
>
> On 24.04.2019 13:25, Iain Buclaw wrote:
> > On Wed, 24 Apr 2019 at 13:03, Kamil Rytarowski wrote:
> >>
> >> On 24.04.2019 03:30, Iain Buclaw wrote:
> >>> On Wed, 24 Apr 2019 at 01:56, Kamil Rytarowski wrote:
>
> On 24.04.2019
Hi!
The introduction of -gstatement-frontiers (and making it the default)
regressed debug info experience on the attached testcases (not including
in the testsuite, as not sure how to model that in the guality testsuite).
The current behavior is that
b test
r
n
n
n
shows the first iteration and
On Thu, Apr 25, 2019 at 9:51 AM Martin Liška wrote:
> On 4/23/19 10:29 AM, Martin Liška wrote:
> > On 4/18/19 7:44 PM, H.J. Lu wrote:
> >> On Thu, Apr 18, 2019 at 4:07 AM Martin Liška wrote:
> >>>
> >>> Hi.
> >>>
> >>> I'm sending updated version of that patch. The patch rejects usage of
>
On 4/23/19 10:29 AM, Martin Liška wrote:
> On 4/18/19 7:44 PM, H.J. Lu wrote:
>> On Thu, Apr 18, 2019 at 4:07 AM Martin Liška wrote:
>>>
>>> Hi.
>>>
>>> I'm sending updated version of that patch. The patch rejects usage of
>>> AVX512 ISAs (except AVX512F)
>>> for target attribute for C++
Hi,
This patch adds PWD_COMMAND to libphobos/testsuite/Makefile.am, which
is used by the parallelized testing machinery. Noticed by some errors
when compiling from a newly set-up build server.
touch: cannot touch '/libphobos-parallel/finished': No such file or directory
make[3]: ***
On April 24, 2019 11:26:28 PM GMT+02:00, Jeff Law wrote:
>On 4/24/19 4:44 AM, Richard Biener wrote:
>>> Given that we can use the lattice copy propagator by just adding the
>>> pass to passes.def whereas using the RPN VN actually requires a
>little
>>> bit of real code (to set up the entry/exits
On April 24, 2019 8:31:44 PM GMT+02:00, Jeff Law wrote:
>On 4/24/19 4:44 AM, Richard Biener wrote:
>> On Tue, Apr 23, 2019 at 4:29 PM Jeff Law wrote:
>>>
>>>
>>> As discussed in the BZ, this patch addresses the false positive
>warning
>>> by cleaning up the const/copy propagations left in the IL
From: David Edelsohn
> I have committed this patch.
>
> Thanks, David
Thanks, I'll warn you if I ever understand what's wrong with it.
Clément
58 matches
Mail list logo
