On 2013/10/11 15:26:04, danno wrote:
I fundamentally don't have an issue with this CL, but I am curious what
the
motivation is behind it?
In my research about aligning stack on MIPS, I have carefully examined
deoptimizer code,
and I had thought it would be more consistent that such a highly organized
C++
code use C++ global new/delete operators
instead of C like malloc and free. No big deal, minor cl that is small
cleanup.
I am sorry, if I break some already established convention and preferred
method
of malloc and free usage in v8
for general allocations and deallocations that I was not aware of
In that case CL can be closed.
https://codereview.chromium.org/26863002/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
