--- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-12-09
21:07 ---
Subject: Bug 18514
CVSROOT:/cvs/gcc
Module name:gcc
Changes by: [EMAIL PROTECTED] 2004-12-09 21:07:01
Modified files:
gcc/cp : ChangeLog name-lookup.c
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-09
00:43 ---
Patch here: http://gcc.gnu.org/ml/gcc-patches/2004-12/msg00645.html.
--
What|Removed |Added
austern at apple dot com [EMAIL PROTECTED] writes:
| So what to do about this? In principle, I think the answer is that
| builtin_function is doing something wrong by calling
| builtin_function_1 twice, once for the global namespace and once for
| namespace std. If we really must define all
--- Additional Comments From gdr at integrable-solutions dot net
2004-11-30 11:46 ---
Subject: Re: [3.4/4.0 Regression] Alternate asm name ignored for redeclared
builtin function imported into namespace std
austern at apple dot com [EMAIL PROTECTED] writes:
| So what to do about
--- Additional Comments From austern at apple dot com 2004-11-29 20:56
---
Yep, I see what the problem is now. When we create a builtin in C++, we create
the declaration in both
the global namespace and namespace std. Later, when we see the declaration of
snprintf in the global
--- Additional Comments From neroden at gcc dot gnu dot org 2004-11-27
00:20 ---
In 3.4.2 (Debian's version), I can import into *any* namespace (xxx, for
instance) and get the same problem. However, it *is* essential that the
function be snprintf, and not bar. fancy_snprintf is
