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:22:12 +0000 [thread overview] Message-ID: <bug-99542-4-LsV7igTDUA@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org, | |rsandifo at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- This is aarch64 backend bug in aarch64_simd_clone_compute_vecsize_and_simdlen. If you look at the i386 counterpart, for argument checking it does: tree type_arg_types = TYPE_ARG_TYPES (TREE_TYPE (node->decl)); bool decl_arg_p = (node->definition || type_arg_types == NULL_TREE); for (t = (decl_arg_p ? DECL_ARGUMENTS (node->decl) : type_arg_types), i = 0; t && t != void_list_node; t = TREE_CHAIN (t), i++) { tree arg_type = decl_arg_p ? TREE_TYPE (t) : TREE_VALUE (t); but aarch64 doesn't bother and instead it does just: for (t = DECL_ARGUMENTS (node->decl); t; t = DECL_CHAIN (t)) { arg_type = TREE_TYPE (t); The problem with that is that it doesn't check the arguments at all for function declarations that aren't definitions.
next prev parent reply other threads:[~2021-03-12 11:22 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 [this message] 2021-03-12 11:23 ` jakub at gcc dot gnu.org 2021-03-12 11:39 ` jakub at gcc dot gnu.org 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-LsV7igTDUA@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: linkBe 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).