This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: C++ PATCHes relating to c++/48834, c++/40975 (array new)

From: Eric Botcazou <ebotcazou at adacore dot com>
To: Jason Merrill <jason at redhat dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Wed, 4 May 2011 10:12:05 +0200
Subject: Re: C++ PATCHes relating to c++/48834, c++/40975 (array new)
References: <4DBF2909.4050207@redhat.com> <201105031752.31600.ebotcazou@adacore.com> <4DC03B43.4060705@redhat.com>

> Well, let's look at the users of copy_tree_r.
>
> cp/tree.c (bot_manip): The case I want to fix.

Then I'd put the fix there.  The old behaviour of copy_tree_r is IMO the most 
sensible one and its callers should cope, as almost all already do it seems.

-- 
Eric Botcazou

Follow-Ups:
- Re: C++ PATCHes relating to c++/48834, c++/40975 (array new)
  - From: Jason Merrill

References:
- C++ PATCHes relating to c++/48834, c++/40975 (array new)
  - From: Jason Merrill
- Re: C++ PATCHes relating to c++/48834, c++/40975 (array new)
  - From: Eric Botcazou
- Re: C++ PATCHes relating to c++/48834, c++/40975 (array new)
  - From: Jason Merrill

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]