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/93524] [ISO C Binding][F2018] CFI_allocate – elem_size mishandled + sm wrongly set? Date: Thu, 24 Jun 2021 01:00:29 +0000 [thread overview] Message-ID: <bug-93524-4-WpspqZNN4R@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93524-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93524 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Sandra Loosemore <sandra@gcc.gnu.org>: https://gcc.gnu.org/g:1a2bbc08d9e5e4837d33afbb8c8347a182223a43 commit r11-8648-g1a2bbc08d9e5e4837d33afbb8c8347a182223a43 Author: Sandra Loosemore <sandra@codesourcery.com> Date: Tue Jun 22 12:42:17 2021 -0700 Fortran: fix sm computation in CFI_allocate [PR93524] Backported from trunk. This patch fixes a bug in setting the step multiplier field in the C descriptor for array dimensions > 2. 2021-06-21 Sandra Loosemore <sandra@codesourcery.com> Tobias Burnus <tobias@codesourcery.com> libgfortran/ PR fortran/93524 * runtime/ISO_Fortran_binding.c (CFI_allocate): Fix sm computation. gcc/testsuite/ PR fortran/93524 * gfortran.dg/pr93524.c: New. * gfortran.dg/pr93524.f90: New.
next prev parent reply other threads:[~2021-06-24 1:00 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93524-4@http.gcc.gnu.org/bugzilla/> 2021-01-11 16:18 ` burnus at gcc dot gnu.org 2021-01-16 13:03 ` burnus at gcc dot gnu.org 2021-01-16 13:05 ` dominiq at lps dot ens.fr 2021-01-28 7:33 ` tkoenig at gcc dot gnu.org 2021-06-22 19:46 ` cvs-commit at gcc dot gnu.org 2021-06-22 19:52 ` sandra at gcc dot gnu.org 2021-06-24 1:00 ` cvs-commit at gcc dot gnu.org [this message] 2021-06-24 1:07 ` sandra at gcc dot gnu.org 2021-08-31 10:55 ` burnus 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-93524-4-WpspqZNN4R@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).