public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "milan.durovic at ali dot com.au" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67739] name clash between builtin functions and local variables when optimization is on
Date: Mon, 28 Sep 2015 21:05:00 -0000	[thread overview]
Message-ID: <bug-67739-4-Lb5SUsLnB1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67739-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67739

--- Comment #3 from Milan Durovic <milan.durovic at ali dot com.au> ---
I think a warning is the right answer. You can't expect people to be aware of
all built-in functions. I wasn't aware that there was such a function called
'sincos'.

And even more importantly, the name clash is not really obvious for the simple
reason that the function that the compiler invokes is not even explicitly
exposed, ie. it doesn't appear in the source code. And these change: in one
version, compiler invokes sincosf and in another, sincos. So code that compiles
and works fine with one compiler version would fail with another compiler
version.

Warning is the minimum that should happen, although I think if the compiler
wants to invoke a particular, hidden function, and its name clashes with a
program variable, then it's something compiler should automatically resolve.


  parent reply	other threads:[~2015-09-28 21:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28  6:09 [Bug c++/67739] New: " milan.durovic at ali dot com.au
2015-09-28 11:02 ` [Bug c++/67739] " rguenth at gcc dot gnu.org
2015-09-28 21:05 ` milan.durovic at ali dot com.au [this message]
2015-09-28 21:20 ` milan.durovic at ali dot com.au
2024-03-11  1:07 ` [Bug middle-end/67739] " pinskia at gcc dot gnu.org

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-67739-4-Lb5SUsLnB1@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).