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/103627] ICE: in extract_insn, at recog.c:2769 (error: unrecognizable insn)
Date: Tue, 15 Feb 2022 09:51:58 +0000	[thread overview]
Message-ID: <bug-103627-4-BmXEQSIArG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103627-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:99ac7ce34348889125230687d8277cd1df22027a

commit r10-10457-g99ac7ce34348889125230687d8277cd1df22027a
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Sun Feb 6 21:30:02 2022 -0600

    rs6000: Move the hunk affecting VSX/ALTIVEC ahead [PR103627]

    The modified hunk can update VSX and ALTIVEC flag, we have some codes
    to check/warn for some flags related to VSX and ALTIVEC sitting where
    the hunk is proprosed to be moved to.  Without this adjustment, the
    VSX and ALTIVEC update is too late, it can cause the incompatibility
    and result in unexpected behaviors, the associated test case is one
    typical case.

    Since we already have the code which sets TARGET_FLOAT128_TYPE and lays
    after the moved place, and OPTION_MASK_FLOAT128_KEYWORD will rely on
    TARGET_FLOAT128_TYPE, so it just simply remove them.

    gcc/ChangeLog:

            PR target/103627
            * config/rs6000/rs6000.c (rs6000_option_override_internal): Move
the
            hunk affecting VSX and ALTIVEC to appropriate place.

    gcc/testsuite/ChangeLog:

            PR target/103627
            * gcc.target/powerpc/pr103627-3.c: New test.

    (cherry picked from commit e66ba0f55c000152df63fc67c11a64f79122ef86)

  parent reply	other threads:[~2022-02-15  9:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 11:08 [Bug target/103627] New: " asolokha at gmx dot com
2021-12-10 10:05 ` [Bug target/103627] " linkw at gcc dot gnu.org
2021-12-10 10:40 ` linkw at gcc dot gnu.org
2021-12-20  5:20 ` linkw at gcc dot gnu.org
2021-12-20  5:29 ` linkw at gcc dot gnu.org
2022-02-07  5:48 ` cvs-commit at gcc dot gnu.org
2022-02-07  5:48 ` cvs-commit at gcc dot gnu.org
2022-02-15  7:26 ` asolokha at gmx dot com
2022-02-15  9:50 ` cvs-commit at gcc dot gnu.org
2022-02-15  9:50 ` cvs-commit at gcc dot gnu.org
2022-02-15  9:51 ` cvs-commit at gcc dot gnu.org
2022-02-15  9:51 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-15  9:53 ` linkw 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-103627-4-BmXEQSIArG@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).