From: JunMa <JunMa@linux.alibaba.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, Nathan Sidwell <nathan@acm.org>
Subject: Re: [PING PATCH coroutines] Set side effects flag for BIND_EXPR which build in maybe_promote_captured_temps
Date: Fri, 06 Mar 2020 05:44:00 -0000 [thread overview]
Message-ID: <d8c594ae-7a50-4221-94b4-dd29391366a8@linux.alibaba.com> (raw)
In-Reply-To: <820841F1-826B-48EA-8AC2-2F7EC46987D9@sandoe.co.uk>
å¨ 2020/3/5 ä¸å9:51, Iain Sandoe åé:
> Hello JunMa,
>
> JunMa <JunMa@linux.alibaba.com> wrote:
>
>> Ping
>
> Thanks for your patch(es) and I am sorry this has taken some time to
> review.
>
> (right now, weâre trying to ensure that we have the latest standard
> represented in
> Â GCC10, so updating to n4849).
>>
>> å¨ 2020/2/27 ä¸å10:17, JunMa åé:
>>> å¨ 2020/2/11 ä¸å10:50, JunMa åé:
>>> Hi
>>> kindly ping~
>>>
>>> Regards
>>> JunMa
>>>> Hi
>>>> As title. in maybe_promote_captured_temps, we promote captured
>>>> temporaries
>>>> and co_await_expr into a new BIND_EXPR. As the BIND_EXPR contains
>>>> co_await_expr and maybe other function calls, the side effects flag
>>>> should
>>>> be set.
>>>>
>>>> This patch fix one mismatch in cppcoro, the testcase comes from
>>>> cppcoro
>>>> and is reduced by creduce.
>
> With the following test conditions;
>
> r10-7040-ga2ec7c4aafbcd517
> Â + the two approved patches by Bin Cheng applied.
>
> Â 1/ the test case in this patch (lambda-10-co-await-lambda.C) fails
> both with and without the patch.
> Â 2/ the patch regresses one of my local testcases.
>
The test case fails because of ICE which is fixed by the
[PING PATCH coroutines] Do not strip cleanup_point when promote
temporaries out of current stmt
This patch fix the runtime mismatch.
The extra regression is co-await-syntax-11.C which comes from Bin's
patch and also is fixed by that
patch.
Regards
JunMa
> So, it appears that the testcase might show a bug - but the fix is not
> the right one for current trunk?
>
> Please could you re-check ?
>
> thanks
> Iain
prev parent reply other threads:[~2020-03-06 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 2:50 [PATCH " JunMa
2020-02-11 8:45 ` JunMa
2020-02-27 2:17 ` [PING PATCH " JunMa
2020-03-05 11:55 ` JunMa
2020-03-05 13:52 ` Iain Sandoe
2020-03-06 5:44 ` JunMa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d8c594ae-7a50-4221-94b4-dd29391366a8@linux.alibaba.com \
--to=junma@linux.alibaba.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=nathan@acm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).