Re: gcc 4.5.1 -fstrict-aliasing and store removal

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Vyacheslav Egorov <vegorov@xxxxxxxxxxxx> writes:

> On Sat, Oct 2, 2010 at 12:37 AM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote:
>> Well, also, you need to allocate Object* values using malloc or placement new, not, say, new
>> char[].
>
> We use a custom allocators which do not rely on any of these [we mmap
> pages and treat pieces of mmap'ed pages as objects]. Is this a
> problem?

That should be fine.  Anything which essentially acts like malloc should
be fine.  The difference is that new char[] returns memory which already
has a type, and malloc or mmap do not.

Ian


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux