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 fortran/93660] Decl mismatch between fndecl TYPE and used arglist / ICE in ipa_simd_modify_function_body, at omp-simd-clone.c:993
Date: Tue, 30 Mar 2021 08:35:21 +0000 [thread overview]
Message-ID: <bug-93660-4-N1iXxDITmZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93660-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93660
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Christophe Lyon
<clyon@gcc.gnu.org>:
https://gcc.gnu.org/g:960eaefb99a805dd6afdc1f223055bd2458d6c49
commit r10-9617-g960eaefb99a805dd6afdc1f223055bd2458d6c49
Author: Jakub Jelinek <jakub@redhat.com>
Date: Mon Mar 29 17:05:47 2021 +0200
testsuite: Expect a warning on aarch64 for declare-simd-coarray-lib.f90
[PR93660]
aarch64 currently doesn't support declare simd where the return value and
arguments
have different sizes and warns about that case. This change adds a
dg-warning
for that case like various other tests have already.
2021-03-29 Jakub Jelinek <jakub@redhat.com>
PR fortran/93660
* gfortran.dg/gomp/declare-simd-coarray-lib.f90: Expect a mixed
size
declare simd warning on aarch64.
prev parent reply other threads:[~2021-03-30 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-93660-4@http.gcc.gnu.org/bugzilla/>
2021-03-11 14:30 ` burnus at gcc dot gnu.org
2021-03-15 13:51 ` burnus at gcc dot gnu.org
2021-03-23 14:46 ` cvs-commit at gcc dot gnu.org
2021-03-25 10:22 ` cvs-commit at gcc dot gnu.org
2021-03-26 7:43 ` burnus at gcc dot gnu.org
2021-03-29 14:51 ` clyon at gcc dot gnu.org
2021-03-29 15:03 ` burnus at gcc dot gnu.org
2021-03-29 15:07 ` cvs-commit at gcc dot gnu.org
2021-03-30 8:35 ` cvs-commit at gcc dot gnu.org [this message]
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-93660-4-N1iXxDITmZ@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).