public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/100755] Error with fortran object (v11.1.0) Date: Tue, 25 May 2021 18:58:26 +0000 [thread overview] Message-ID: <bug-100755-4-TH5q5coNqD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100755-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100755 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|ice-on-valid-code |ice-on-invalid-code CC| |anlauf at gcc dot gnu.org --- Comment #2 from anlauf at gcc dot gnu.org --- Possibly related: PR100283. Note that this is more likely an ice-on-invalid, as the specific intrinsics min0/max accept only default integers as argument. (F2018 table 16.3). 127_8 is not of default integer kind. Accepting non-default integers is an extension.
next prev parent reply other threads:[~2021-05-25 18:58 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-25 15:27 [Bug fortran/100755] New: " afernandez at odyhpc dot com 2021-05-25 15:42 ` [Bug fortran/100755] " marxin at gcc dot gnu.org 2021-05-25 18:58 ` anlauf at gcc dot gnu.org [this message] 2021-05-25 21:10 ` [Bug middle-end/100755] " afernandez at odyhpc dot com 2021-05-25 22:04 ` dominiq at lps dot ens.fr 2021-05-26 0:11 ` afernandez at odyhpc dot com 2021-05-26 6:42 ` anlauf at gcc dot gnu.org 2021-05-26 13:43 ` afernandez at odyhpc dot com 2021-06-18 17:52 ` anlauf at gcc dot gnu.org 2022-01-01 9:04 ` pinskia 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-100755-4-TH5q5coNqD@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).