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/99820] aarch64: ICE (segfault) in aarch64_analyze_loop_vinfo with -moverride=tune=use_new_vector_costs
Date: Tue, 30 Mar 2021 15:43:10 +0000	[thread overview]
Message-ID: <bug-99820-4-Utr3M2GhRV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99820-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kyrylo Tkachov <ktkachov@gcc.gnu.org>:

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

commit r11-7913-gc277abd9cd3d10db59f9965d7d6356868da42a9f
Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Date:   Tue Mar 30 16:42:17 2021 +0100

    aarch64: PR target/99820: Guard on available SVE issue info before using

    This fixes a simple segfault ICE when using the use_new_vector_costs
tunable with a CPU tuning that it wasn't intended for.
    I'm not adding a testcase here as we intend to remove the tunable for GCC
12 anyway (the new costing logic will remain and will benefit
    from this extra check, but the -moverride option will no longer exist).

    gcc/ChangeLog:

            PR target/99820
            * config/aarch64/aarch64.c (aarch64_analyze_loop_vinfo): Check for
            available issue_info before using it.

  parent reply	other threads:[~2021-03-30 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 20:04 [Bug target/99820] New: " acoplan at gcc dot gnu.org
2021-03-29 20:05 ` [Bug target/99820] " acoplan at gcc dot gnu.org
2021-03-30 15:43 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-30 15:44 ` ktkachov 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-99820-4-Utr3M2GhRV@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).