public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94538] [10 Regression] ICE: in extract_constrain_insn_cached, at recog.c:2223 (insn does not satisfy its constraints) with -mcpu=cortex-m23 -mslow-flash-data
Date: Fri, 10 Apr 2020 23:42:37 +0000	[thread overview]
Message-ID: <bug-94538-4-1FLFuX2Wpr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94538-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94538

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>:

https://gcc.gnu.org/g:0666767eb4cc864f00ba34d97b9d58f8dc650bba

commit r10-7682-g0666767eb4cc864f00ba34d97b9d58f8dc650bba
Author: Iain Sandoe <iain@sandoe.co.uk>
Date:   Fri Apr 10 20:55:10 2020 +0100

    coroutines: Revise await expansions [PR94528]

    The expansions for await expressions were specific to particular
    cases, this revises it to be more generic.

    a: Revise co_await statement walkers.

    We want to process the co_awaits one statement at a time.
    We also want to be able to determine the insertion points for
    new bind scopes needed to cater for temporaries that are
    captured by reference and have lifetimes that need extension
    to the end of the full expression.  Likewise, the handling of
    captured references in the evaluation of conditions might
    result in the need to make a frame copy.

    This reorganises the statement walking code to make it easier to
    extend for these purposes.

    b: Factor reference-captured temp code.

    We want to be able to use the code that writes a new bind expr
    with vars (and their initializers) from several places, so split
    that out of the maybe_promote_captured_temps() function into a
    new replace_statement_captures ().  Update some comments.

    c: Generalize await statement expansion.

    This revises the expansion to avoid the need to expand conditionally
    on the tree type.  It resolves PR 94528.

    gcc/cp/ChangeLog:

    2020-04-10  Iain Sandoe  <iain@sandoe.co.uk>

            PR c++/94538
            * coroutines.cc (co_await_expander): Remove.
            (expand_one_await_expression): New.
            (process_one_statement): New.
            (await_statement_expander): New.
            (build_actor_fn): Revise to use per-statement expander.
            (struct susp_frame_data): Reorder and comment.
            (register_awaits): Factor code.
            (replace_statement_captures): New, factored from...
            (maybe_promote_captured_temps):.. here.
            (await_statement_walker): Revise to process per statement.
            (morph_fn_to_coro): Use revised susp_frame_data layout.

    gcc/testsuite/ChangeLog:

    2020-04-10  Iain Sandoe  <iain@sandoe.co.uk>

            PR c++/94538
            * g++.dg/coroutines/pr94528.C: New test.

  parent reply	other threads:[~2020-04-10 23:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 11:02 [Bug target/94538] New: [9/10 " zsojka at seznam dot cz
2020-04-09 13:38 ` [Bug target/94538] " wilco at gcc dot gnu.org
2020-04-09 16:35 ` [Bug target/94538] [10 " wilco at gcc dot gnu.org
2020-04-09 17:46 ` zsojka at seznam dot cz
2020-04-09 18:08 ` wilco at gcc dot gnu.org
2020-04-10 23:42 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-10 23:51 ` iains at gcc dot gnu.org
2020-04-14 11:28 ` wilco at gcc dot gnu.org
2020-04-14 12:16 ` clyon at gcc dot gnu.org
2020-04-14 12:54 ` zsojka at seznam dot cz
2020-04-14 14:42 ` wilco at gcc dot gnu.org
2020-04-14 17:08 ` clyon at gcc dot gnu.org
2020-04-16 15:40 ` clyon at gcc dot gnu.org
2020-04-16 16:44 ` wilco at gcc dot gnu.org
2020-04-16 17:10 ` wilco at gcc dot gnu.org
2020-04-16 19:41 ` clyon at gcc dot gnu.org
2020-04-17 10:23 ` wilco at gcc dot gnu.org
2020-04-30  7:27 ` [Bug target/94538] [9/10 " rguenth at gcc dot gnu.org
2020-04-30  9:44 ` clyon at gcc dot gnu.org
2020-04-30 12:28 ` wilco at gcc dot gnu.org
2020-08-24  9:09 ` [Bug target/94538] [9/10/11 " cvs-commit at gcc dot gnu.org
2020-08-24 13:32 ` clyon at gcc dot gnu.org
2020-08-27 11:12 ` cvs-commit at gcc dot gnu.org
2020-08-27 11:18 ` cvs-commit at gcc dot gnu.org
2020-08-27 11:19 ` clyon at gcc dot gnu.org

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=bug-94538-4-1FLFuX2Wpr@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).