public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99542] [9/10/11 Regression] ICE in exact_div, at poly-int.h:2219
Date: Fri, 12 Mar 2021 11:39:54 +0000	[thread overview]
Message-ID: <bug-99542-4-kyMesawcct@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99542-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 50374
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50374&action=edit
gcc11-pr99542.patch

Untested fix.  There is another difference from i386, for !TREE_PUBLIC
(node->decl) the i386 version never returns > 1, but instead just provides the
version which is the best for the current TU.  Wouldn't it make sense on
aarch64 too?  Or does it hope that the unused entrypoints will be optimized
away?
I'm not sure it happens, because simd cloning is fairly late IPA pass.

  parent reply	other threads:[~2021-03-12 11:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11  6:05 [Bug target/99542] New: " asolokha at gmx dot com
2021-03-11  8:44 ` [Bug target/99542] " rguenth at gcc dot gnu.org
2021-03-12 11:22 ` jakub at gcc dot gnu.org
2021-03-12 11:23 ` jakub at gcc dot gnu.org
2021-03-12 11:39 ` jakub at gcc dot gnu.org [this message]
2021-03-16  9:35 ` cvs-commit at gcc dot gnu.org
2021-03-16  9:51 ` [Bug target/99542] [9/10 " jakub at gcc dot gnu.org
2021-03-16 21:51 ` cvs-commit at gcc dot gnu.org
2021-03-17 11:15 ` cvs-commit at gcc dot gnu.org
2021-03-19 23:30 ` cvs-commit at gcc dot gnu.org
2021-03-19 23:30 ` cvs-commit at gcc dot gnu.org
2021-03-20  8:09 ` [Bug target/99542] [9 " jakub at gcc dot gnu.org
2021-04-20 23:33 ` cvs-commit at gcc dot gnu.org
2021-04-20 23:33 ` cvs-commit at gcc dot gnu.org
2021-04-22 13:40 ` jakub 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-99542-4-kyMesawcct@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).