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/100302] [11/12 Regression] ICE in abs_hwi, at hwint.h:324 since r11-7861
Date: Thu, 29 Apr 2021 09:36:53 +0000	[thread overview]
Message-ID: <bug-100302-4-14gQqaunmn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100302-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:5ac1313f32c5cd875ad047f6575dd4608e1949cf

commit r11-8326-g5ac1313f32c5cd875ad047f6575dd4608e1949cf
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Apr 29 11:34:50 2021 +0200

    aarch64: Fix ICE in aarch64_add_offset_1_temporaries [PR100302]

    In PR94121 I've changed aarch64_add_offset_1 to use absu_hwi instead of
    abs_hwi because offset can be HOST_WIDE_INT_MIN.  As can be seen with
    the testcase below, aarch64_add_offset_1_temporaries suffers from the same
    problem and should be in sync with aarch64_add_offset_1, i.e. for
    HOST_WIDE_INT_MIN it needs a temporary.

    2021-04-29  Jakub Jelinek  <jakub@redhat.com>

            PR target/100302
            * config/aarch64/aarch64.c (aarch64_add_offset_1_temporaries): Use
            absu_hwi instead of abs_hwi.

            * gcc.target/aarch64/sve/pr100302.c: New test.

    (cherry picked from commit 1bb3e2c0ce6ed363c72caf814a6ba6d7b17c3e0a)

  parent reply	other threads:[~2021-04-29  9:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28  3:31 [Bug target/100302] New: ICE in abs_hwi, at hwint.h:324 asolokha at gmx dot com
2021-04-28  8:01 ` [Bug target/100302] " jakub at gcc dot gnu.org
2021-04-28  8:04 ` jakub at gcc dot gnu.org
2021-04-28  8:29 ` [Bug target/100302] [11/12 Regression] ICE in abs_hwi, at hwint.h:324 since r11-7861 jakub at gcc dot gnu.org
2021-04-28  8:42 ` jakub at gcc dot gnu.org
2021-04-28  9:26 ` jakub at gcc dot gnu.org
2021-04-29  9:35 ` cvs-commit at gcc dot gnu.org
2021-04-29  9:36 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-29  9:37 ` jakub at gcc dot gnu.org
2021-05-04 12:08 ` cvs-commit at gcc dot gnu.org
2021-05-04 12:22 ` cvs-commit at gcc dot gnu.org
2021-05-04 12:26 ` cvs-commit 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-100302-4-14gQqaunmn@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).