Putting builtins in the std namespace

Phil Edwards pedwards@disaster.jaj.com
Wed Oct 18 12:19:00 GMT 2000

On Wed, Oct 18, 2000 at 12:00:31PM -0700, Mark Mitchell wrote:
> >>>>> "Phil" == Phil Edwards <pedwards@disaster.jaj.com> writes:
>     Phil> On Wed, Oct 18, 2000 at 09:43:12AM -0700, Mark Mitchell
>     Phil> wrote:
>     >> Here's a first cut.  This patch doesn't move builtins whose
>     >> names start with a `_' since those are already reserved names,
>     >> and since I bet a lot of macros depend on them.
>     Phil> That may be what's causing the problem below.  (That's my
>     Phil> first cut at diagnosis.)
> Ugh.  I'll try a V3 build, and see what happens.  Without -fhonor-std,
> this patch shouldn't change the builtins, so I'm not sure what's going
> on.

I guess I wasn't clear:  the error I reported occurs while /building/
v3, not while using it.  Enabling v3 turns on -fhonor-std by default.
I haven't tried building with -v2 (and don't plan to).


pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools.  Fools are protected by more capable fools.

More information about the Gcc-patches mailing list