public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/102708] Improve ''array temporary was created for argument" diagnostic Date: Thu, 06 Jan 2022 01:21:21 +0000 [thread overview] Message-ID: <bug-102708-4-n2ioD8ok6R@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102708-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102708 sandra at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sandra at gcc dot gnu.org --- Comment #2 from sandra at gcc dot gnu.org --- I fixed a lot of bugs with creating excessive temporaries for calls to bind(c) functions in my fix for PR 103390 (commit 6447f6f983ffeaecb8753ef685d702bf2594968b). I'm not sure if there is more to do there or not, but it seems unrelated to the original problem. If there's a bug, it ought to be in its own issue. IIUC what needs to be done for the original problem is fixing (all?) the calls to gfc_conv_subref_array_arg to pass the fsym and proc_name arguments.
prev parent reply other threads:[~2022-01-06 1:21 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-12 15:00 [Bug fortran/102708] New: " burnus at gcc dot gnu.org 2021-10-14 9:49 ` [Bug fortran/102708] " burnus at gcc dot gnu.org 2022-01-06 1:21 ` sandra 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-102708-4-n2ioD8ok6R@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).