public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107091] Misleading error message "incompatible types when returning ..."
Date: Thu, 29 Sep 2022 21:18:02 +0000 [thread overview]
Message-ID: <bug-107091-4-b5KkVdizD4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107091-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107091
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2022-09-29
Status|UNCONFIRMED |NEW
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
clang produces:
<source>:3:12: error: returning 'void *' from a function with incompatible
result type 'double'
return (void *)0;
^~~~~~~~~
MSVC produces:
<source>(3): error C2440: 'return': cannot convert from 'void *' to 'double'
ICC Produces:
<source>(3): error: return value type does not match the function type
return (void *)0;
^
cproc (https://github.com/michaelforney/cproc) produces:
<source>:2:22: error: assignment to arithmetic type must be from arithmetic
type
MSVC seems similar to what is produced for GCC's C++ front-end.
I don't know the best wording here really because convert might even be wrong.
prev parent reply other threads:[~2022-09-29 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 18:30 [Bug c/107091] New: " Keith.S.Thompson at gmail dot com
2022-09-29 21:18 ` pinskia 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-107091-4-b5KkVdizD4@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).