public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/101123] [11/12 Regression] Invalid code for MAX0 with -fdefault-integer-8 Date: Fri, 18 Jun 2021 16:28:12 +0000 [thread overview] Message-ID: <bug-101123-4-4mgkDjDd83@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101123-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101123 Dominique d'Humieres <dominiq at lps dot ens.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING --- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- I think this PR should be closed as invalid. When using -fdefault_*, it is the user's responsibility to check that the promotion is compatible with procedure arguments: MAX0 is expecting INTEGER(4) and is given INTEGER(8). The code compiles if MAX0 is replaced with the generic function MAX.
next prev parent reply other threads:[~2021-06-18 16:28 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-18 13:03 [Bug fortran/101123] New: " rguenth at gcc dot gnu.org 2021-06-18 13:04 ` [Bug fortran/101123] " rguenth at gcc dot gnu.org 2021-06-18 13:29 ` jakub at gcc dot gnu.org 2021-06-18 16:23 ` anlauf at gcc dot gnu.org 2021-06-18 16:28 ` dominiq at lps dot ens.fr [this message] 2021-06-18 16:40 ` anlauf at gcc dot gnu.org 2021-06-18 16:44 ` jakub at gcc dot gnu.org 2021-06-18 17:25 ` anlauf at gcc dot gnu.org 2021-06-18 17:34 ` cvs-commit at gcc dot gnu.org 2021-06-19 18:16 ` cvs-commit at gcc dot gnu.org 2021-06-19 18:19 ` 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-101123-4-4mgkDjDd83@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).