public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rimvydas.jas at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/102079] New: Misleading -Wlto-type-mismatch warning on wrong float type to C function Date: Thu, 26 Aug 2021 14:04:00 +0000 [thread overview] Message-ID: <bug-102079-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102079 Bug ID: 102079 Summary: Misleading -Wlto-type-mismatch warning on wrong float type to C function Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: rimvydas.jas at gmail dot com Target Milestone: --- $ cat bar.c #include <stddef.h> void bar_ (char *cdname, /*float*/ double *pkey, char *cdfile, size_t cdname_len, size_t cdfile_len) { }; $ cat foo.f90 program test call foo('start','loo',13.) end program subroutine foo(cdname,cdfile,pkey) implicit none character(len=*) :: cdname,cdfile real :: pkey call bar(cdname,pkey,cdfile) end subroutine $ gcc -flto -c bar.c $ gfortran -Wall -Wextra -flto foo.f90 bar.o foo.f90:9:28: warning: type of 'bar' does not match original declaration [-Wlto-type-mismatch] 9 | call bar(cdname,pkey,cdfile) | ^ bar.c:2:6: note: type mismatch in parameter 4 2 | void bar_ (char *cdname, /*float*/ double *pkey, char *cdfile, size_t cdname_len, size_t cdfile_len) { }; | ^ bar.c:2:6: note: type 'size_t' should match type 'long int' bar.c:2:6: note: 'bar_' was previously declared here bar.c:2:6: note: code may be misoptimized unless '-fno-strict-aliasing' is used Actual hard error is typo in bar.c for "float *pkey" 2nd argument and not a first hidden argument for first character array length.
next reply other threads:[~2021-08-26 14:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-26 14:04 rimvydas.jas at gmail dot com [this message] 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 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@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).