public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <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: Mon, 27 Sep 2021 07:40:36 +0000	[thread overview]
Message-ID: <bug-102079-4-e69gDwakqw@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

--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> ---
On Sun, 26 Sep 2021, hubicka at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102079
> 
> --- Comment #3 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
> I think the problem here is that fortran uses "long int" while size_t
> interoperate with "unsigned long int".
> Does fortran standard promise that the value should inter-operate with size_t
> as well?

Note my point was that the TBAA warning is unnecessary since at least
singed and unsigned variants of the same type inter-operate in that
respect.  Can we fix that independently of the issue of
value inter-operation here?

      parent reply	other threads:[~2021-09-27  7:40 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
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 [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-102079-4-e69gDwakqw@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).