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/103097] ICE in move_for_stack_reg, at reg-stack.c:1186
Date: Thu, 09 Dec 2021 02:39:08 +0000	[thread overview]
Message-ID: <bug-103097-4-whKA1x2ZXL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103097-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Alexandre Oliva <aoliva@gcc.gnu.org>:

https://gcc.gnu.org/g:af93386ffc18ca6c7d1949751ff97cc6ce092b2c

commit r12-5853-gaf93386ffc18ca6c7d1949751ff97cc6ce092b2c
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Wed Dec 8 23:37:15 2021 -0300

    [PR103097] tolerate reg-stack cross-block malformed asms

    The testcase shows malformed asms in one block confuse reg-stack logic
    in another block.  Moving the resetting of any_malformed_asm to the
    end of the pass enables it to take effect throughout the affected
    function.


    for  gcc/ChangeLog

            PR target/103097
            * reg-stack.c (convert_regs_1): Move any_malformed_asm
            resetting...
            (reg_to_stack): ... here.

    for  gcc/testsuite/ChangeLog

            PR target/103097
            * gcc.target/i386/pr103097.c: New.

  parent reply	other threads:[~2021-12-09  2:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 11:06 [Bug target/103097] New: " asolokha at gmx dot com
2021-11-05 11:33 ` [Bug target/103097] " marxin at gcc dot gnu.org
2021-11-19 12:49 ` aoliva at gcc dot gnu.org
2021-12-09  2:39 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-09  2:53 ` aoliva 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-103097-4-whKA1x2ZXL@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).