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/99542] [9/10 Regression] ICE in exact_div, at poly-int.h:2219
Date: Fri, 19 Mar 2021 23:30:36 +0000	[thread overview]
Message-ID: <bug-99542-4-g1w09j7sFJ@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 #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:06589d2232abc92ac9bcb43e4a4ec64ead627752

commit r10-9485-g06589d2232abc92ac9bcb43e4a4ec64ead627752
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Mar 16 10:34:44 2021 +0100

    aarch64: Fix up aarch64_simd_clone_compute_vecsize_and_simdlen [PR99542]

    As the patch shows, there are several bugs in
    aarch64_simd_clone_compute_vecsize_and_simdlen.
    One is that unlike for function declarations that aren't definitions
    it completely ignores argument types.  Such decls don't have
DECL_ARGUMENTS,
    but we can walk TYPE_ARG_TYPES instead, like the i386 backend does or like
    the simd cloning code in the middle end does too.

    Another problem is that it checks types of uniform arguments.  That is
    unnecessary, uniform arguments are passed the way it normally is, it is
    a scalar argument rather than vector, so there is no reason not to support
    uniform argument of different size, or long double, structure etc.

    2021-03-16  Jakub Jelinek  <jakub@redhat.com>

            PR target/99542
            * config/aarch64/aarch64.c
            (aarch64_simd_clone_compute_vecsize_and_simdlen): If not a function
            definition, walk TYPE_ARG_TYPES list if non-NULL for argument types
            instead of DECL_ARGUMENTS.  Ignore types for uniform arguments.

            * gcc.dg/gomp/pr99542.c: New test.
            * gcc.dg/gomp/pr59669-2.c (bar): Don't expect a warning on aarch64.
            * gcc.dg/gomp/simd-clones-2.c (setArray): Likewise.
            * g++.dg/vect/simd-clone-7.cc (bar): Likewise.
            * g++.dg/gomp/declare-simd-1.C (f37): Expect a different warning
            on aarch64.
            * gcc.dg/declare-simd.c (fn2): Expect a new warning on aarch64.

    (cherry picked from commit fcefc59befd396267b824c170b6a37acaf10874e)

  parent reply	other threads:[~2021-03-19 23:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11  6:05 [Bug target/99542] New: [9/10/11 " 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
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 [this message]
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-g1w09j7sFJ@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).