From: Thomas Koenig <tkoenig@netcologne.de>
To: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: *ping* [patch, fortran] Correct fndecls for some library functions
Date: Sat, 21 Nov 2020 09:16:50 +0100 [thread overview]
Message-ID: <51bbd9ab-c8c2-76fc-ae1b-2b92fa829d33@netcologne.de> (raw)
In-Reply-To: <7d637428-5aab-f3f6-e698-ecaf93084c96@netcologne.de>
> this patch makes sure that we pass the correct fn decls for
> some of our library functions. cshift and others still remain
> to be implemented.
>
> This is a step in our voyage to stop lying to the middle end :-)
>
> Regression-tested. OK for trunk?
Ping?
(I am not 100% sure this mail ever made it to the mailing list,
but it is in the archive at
https://gcc.gnu.org/pipermail/fortran/2020-November/055303.html
).
next prev parent reply other threads:[~2020-11-21 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 17:52 Thomas Koenig
2020-11-21 8:16 ` Thomas Koenig [this message]
2020-11-23 21:29 ` *ping* " Iain Sandoe
2020-11-23 22:16 ` Thomas Koenig
2020-11-25 11:58 ` Tobias Burnus
2020-11-27 15:46 ` Tobias Burnus
2020-11-28 11:42 ` Thomas Koenig
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=51bbd9ab-c8c2-76fc-ae1b-2b92fa829d33@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).