public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/102079] Misleading -Wlto-type-mismatch warning on wrong float type to C function
Date: Thu, 26 Aug 2021 14:17:15 +0000 [thread overview]
Message-ID: <bug-102079-4-lbaE9GRXNt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102079-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102079
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Keywords| |diagnostic, lto
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think LTO complains that the fortran frontend uses ssize_t but the C code
size_t for the hidden length argument.
I think the TBAA warning is bogus here since signed and unsigned long
inter-operate. If the fortran frontend is suggesting size_t then it should
better
also use size_type_node for argument passing.
Honza, shouldn't we suppress the TBAA warning here?
next prev parent reply other threads:[~2021-08-26 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 14:04 [Bug fortran/102079] New: " rimvydas.jas at gmail dot com
2021-08-26 14:07 ` [Bug fortran/102079] " rimvydas.jas at gmail dot com
2021-08-26 14:17 ` rguenth at gcc dot gnu.org [this message]
2021-09-26 11:12 ` hubicka at gcc dot gnu.org
2021-09-26 12:57 ` tkoenig at gcc dot gnu.org
2021-09-26 16:42 ` kargl at gcc dot gnu.org
2021-09-27 7:40 ` rguenther at suse dot de
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-102079-4-lbaE9GRXNt@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).