This is the mail archive of the gcc@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: [RFC] Marking C++ new operator as malloc?

From: "Andrew Pinski" <pinskia at gmail dot com>
To: "Chris Lattner" <clattner at apple dot com>
Cc: "Martin Jambor" <jamborm at matfyz dot cz>, "GCC Mailing List" <gcc at gcc dot gnu dot org>
Date: Thu, 13 Sep 2007 16:38:11 -0700
Subject: Re: [RFC] Marking C++ new operator as malloc?
References: <20070907205343.GA22936@matfyz.cz> <EB93AAC0-964B-42BE-958A-1FF5CA078AE8@apple.com>

On 9/7/07, Chris Lattner <clattner@apple.com> wrote:

> It is unclear whether this is safe.  Nothing in the standard AFAIK
> requires the operator new be implemented in terms of malloc, and
> users are allowed to override it.

I was looking for something else in the standard and found this (5.3.4/7):
[Note: If the library allocation function is called, the pointer
returned is distinct from the pointer to any other object. ]

Which means it has to act like malloc.

-- Pinski

Follow-Ups:
- Re: [RFC] Marking C++ new operator as malloc?
  - From: Gabriel Dos Reis

References:
- [RFC] Marking C++ new operator as malloc?
  - From: Martin Jambor
- Re: [RFC] Marking C++ new operator as malloc?
  - From: Chris Lattner

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