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/100132] Optimization breaks pointer association
Date: Sat, 01 Oct 2022 18:55:33 +0000 [thread overview]
Message-ID: <bug-100132-4-sfNDBBwqqz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100132-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100132
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:8c583871e70f5530907d22a21b0f1d1e7b90e224
commit r10-11015-g8c583871e70f5530907d22a21b0f1d1e7b90e224
Author: José Rui Faustino de Sousa <jrfsousa@gmail.com>
Date: Mon Sep 19 22:00:45 2022 +0200
Fortran: Fix function attributes [PR100132]
gcc/fortran/ChangeLog:
PR fortran/100132
* trans-types.c (create_fn_spec): Fix function attributes when
passing polymorphic pointers.
gcc/testsuite/ChangeLog:
PR fortran/100132
* gfortran.dg/PR100132.f90: New test.
(cherry picked from commit be60aa5b608b5f09fadfeff852a46589ac311a42)
next prev parent reply other threads:[~2022-10-01 18:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 23:38 [Bug fortran/100132] New: " jrfsousa at gmail dot com
2021-04-18 0:20 ` [Bug fortran/100132] " jrfsousa at gmail dot com
2021-04-18 9:43 ` dominiq at lps dot ens.fr
2022-09-18 19:11 ` anlauf at gcc dot gnu.org
2022-09-19 20:21 ` anlauf at gcc dot gnu.org
2022-09-20 18:31 ` cvs-commit at gcc dot gnu.org
2022-10-01 18:17 ` cvs-commit at gcc dot gnu.org
2022-10-01 18:40 ` cvs-commit at gcc dot gnu.org
2022-10-01 18:55 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-01 18:56 ` anlauf at gcc dot gnu.org
2022-10-17 20:36 ` anlauf 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-100132-4-sfNDBBwqqz@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).