From: Jason Merrill <jason@redhat.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Alexandre Oliva <aoliva@redhat.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [C++ PATCH] Don't clear DECL_BUILT_IN_CLASS/DECL_FUNCTION_CODE when redeclaring a builtin if types match
Date: Tue, 09 Oct 2007 19:17:00 -0000 [thread overview]
Message-ID: <470BD2D1.9050403@redhat.com> (raw)
In-Reply-To: <47093C37.9000501@codesourcery.com>
I can see both sides to this, but I tend to agree with Jakub. Code that
really wants to override the builtin will need to use -fno-builtin in
other translation units, so it might as well use it in the translation
unit with the definition for consistency. Yes, this is likely to
confuse people who want to override builtins, but that's going to be
tricky to get right in any case.
The other option would be to add an attribute so glibc can mark the
inlines as "still builtin".
Jason
prev parent reply other threads:[~2007-10-09 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 11:51 Jakub Jelinek
2007-10-07 17:43 ` Mark Mitchell
2007-10-07 19:12 ` Jakub Jelinek
2007-10-07 20:06 ` Mark Mitchell
2007-10-09 19:17 ` Jason Merrill [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=470BD2D1.9050403@redhat.com \
--to=jason@redhat.com \
--cc=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mark@codesourcery.com \
/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).