On Thu, 2020-04-23 at 15:16 -0500, Segher Boessenkool wrote:
> On Thu, Apr 23, 2020 at 08:40:50AM -0600, Jeff Law wrote:
> > On Thu, 2020-04-23 at 15:07 +0200, Richard Biener wrote:
> > > On Thu, Apr 23, 2020 at 2:52 PM Segher Boessenkool
> > > wrote:
> > > > On Thu, Apr 23, 2020 at 02:25:40PM +02
Tested x86_64_linux.
Commited to master, backported to releases/gcc-9.
Jonathan Wakely writes:
> On 23/04/20 13:09 -0700, Thomas Rodgers via Libstdc++ wrote:
>>
>> * include/experimental/net/executor: Mark
>> system_context::system_context() = default.
>
> s/default/delete/ :-)
>
> But
Hi, Richard,
This is the 3rd version of the patch, updated based on your previous comments.
Please take a look at it and let me know whether it’s okay to commit?
Thanks a lot for all your help.
Qing.
gcc/ChangeLog:
2020-04-22 qing zhao
PR c/94230
* common.opt: Add -flarge-
I've just committed this patch. It doesn't change anything externally
visible; it's just a code clean up that prepares the way for another
patch I have in development.
There's no rule how these non-standard "*_exec" patterns should look,
but every one but this has the exec-mask operand last ex
On 4/23/20 4:09 PM, Patrick Palka wrote:
This fixes a ICE coming from mangle.c:write_expression when compiling the
ranges-v3 testsuite; the added testcase is a reduced reproducer of the ICE.
Bootstrapped and regtested on x86_64-pc-linux-gnu, and also tested on the
cmcstl2, fmt and range-v3 libra
On 4/23/20 4:09 PM, Patrick Palka wrote:
In the testcase below, when grokfndecl processes the operator() decl for the
lambda inside the friend function foo, processing_template_decl is rightly 1,
but template_class_depth on the lambda's closure type incorrectly returns 0
instead of 1.
Since proc
On 4/23/20 9:42 AM, Jeff Law wrote:
On Wed, 2020-04-22 at 15:36 -0600, Martin Sebor via Gcc-patches wrote:
When computing the size of an object with a flexible array member
the object size pass doesn't consider that the initializer of such
an object can result in its size being in excess of the
On Thu, 2020-04-23 at 16:05 -0500, Qing Zhao wrote:
> Hi, Richard,
>
> This is the 3rd version of the patch, updated based on your previous
> comments.
>
> Please take a look at it and let me know whether it’s okay to commit?
>
> Thanks a lot for all your help.
>
> Qing.
>
> gcc/ChangeLog:
>
On Thu, Apr 23, 2020 at 02:48:38PM -0400, Jason Merrill wrote:
> On 4/22/20 11:27 PM, Marek Polacek wrote:
> > This test is rejected with a bogus "use of deleted function" error
> > starting with r225705 whereby convert_like_real/ck_base no longer
> > sets LOOKUP_ONLYCONVERTING for user_conv_p conv
On 21/04/20 20:58 +0530, kamlesh kumar via Libstdc++ wrote:
added VERIFY in test and changed the template parameter naming.
diff --git a/libstdc++-v3/include/std/any b/libstdc++-v3/include/std/any
index 6b7e68f0e63..d350d0b2575 100644
--- a/libstdc++-v3/include/std/any
+++ b/libstdc++-v3/include
Hi, Thank you for your quick review :)
This patch refactors tree-ssa-operands.c by wrapping the global
variables into a class, and also removes unused code.
In this version, we now move struct function and gimple stmt
arguments previously in the methods to the object constructor,
so that we avoid
On 24/04/20 00:20 +0100, Jonathan Wakely wrote:
On 21/04/20 20:58 +0530, kamlesh kumar via Libstdc++ wrote:
added VERIFY in test and changed the template parameter naming.
diff --git a/libstdc++-v3/include/std/any b/libstdc++-v3/include/std/any
index 6b7e68f0e63..d350d0b2575 100644
--- a/libstd
Thanks for your suggestions. For safety, I put back
flag_unsafe_math_optimizations.
Attached please find the v3 patch which is suitable for git am. Bootstrap and
tested on aarch64 Linux platform.
Is the v3 patch ok?
>From aafcad7ed5d3d156eee1cabbb4958e2cce7899c6 Mon Sep 17 00:00:00 2001
From: z0
This libgo patch by Eric Fang increases the test timeout to 10
minutes, so that tests can pass on some slow machines. This matches
the timeout for the gc tests. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
483096e3130c468a0e1bd224504b394b42662748
diff --g
On Thu, Apr 23, 2020 at 4:54 PM Eric Botcazou wrote:
>
> > > > What is wrong with DF?
> > >
> > > It's slow and memory hungry?
> >
> > Very true, of course. But can this be significantly better?
>
> That's a good question worth investigating in my opinion, because DF didn't
> quite achieve its in
On Fri, Apr 24, 2020 at 5:05 AM Zhanghaijian (A)
wrote:
>
> Thanks for your suggestions. For safety, I put back
> flag_unsafe_math_optimizations.
> Attached please find the v3 patch which is suitable for git am. Bootstrap and
> tested on aarch64 Linux platform.
> Is the v3 patch ok?
OK.
Thanks
Hi.
One can also have enabled gcc_checking_assert in a release build
and that's why coro_body_contains_bind_expr_p can't be guarded
in a CHECKING_P macro.
I'm going to install it as obvious. I've just tested both release and
non-release builds.
Thanks,
Martin
gcc/cp/ChangeLog:
2020-04-24 Mar
101 - 117 of 117 matches
Mail list logo