- 15 Sep, 2017 1 commit
-
-
cjihrig authored
See: https://github.com/nodejs/llnode/pull/130 Change-Id: Ibce294f7620cd6ab0db4408a8c2b457c3a5aebcd Reviewed-on: https://chromium-review.googlesource.com/650746 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#48021}
-
- 03 Sep, 2017 1 commit
-
-
Ben Noordhuis authored
See: https://github.com/nodejs/llnode/issues/117 Change-Id: Icc2830c8e9096610df33ffdc2f89e74cb1b35662 Reviewed-on: https://chromium-review.googlesource.com/618986Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Ben Noordhuis <info@bnoordhuis.nl> Cr-Commit-Position: refs/heads/master@{#47778}
-
- 10 Jul, 2017 1 commit
-
-
Adam Klein authored
This enforces that its enumeration values fit in a byte, as required by Map's {instance_type} field (and probably other parts of the system). Clang helpfully emits this error message if an enum value goes out of range: enumerator value 256 is not representable in the underlying type 'uint8_t' (aka 'unsigned char') Change-Id: I533cd5afc755e7163c2fd40f7b00d9adfd960895 Reviewed-on: https://chromium-review.googlesource.com/565892Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Commit-Queue: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#46544}
-
- 30 Jun, 2017 1 commit
-
-
Mathias Bynens authored
The `FAST_` prefix doesn’t make much sense — they’re all just different cases with their own optimizations. Packedness being implicit (e.g. `FAST_ELEMENTS` vs. `FAST_HOLEY_ELEMENTS`) is not ideal, either. This patch renames the FAST elements kinds as follows: - e.g. FAST_ELEMENTS => PACKED_ELEMENTS - e.g. FAST_HOLEY_ELEMENTS => HOLEY_ELEMENTS The following exceptions are left intact, for lack of a better name: - FAST_SLOPPY_ARGUMENTS_ELEMENTS - SLOW_SLOPPY_ARGUMENTS_ELEMENTS - FAST_STRING_WRAPPER_ELEMENTS - SLOW_STRING_WRAPPER_ELEMENTS This makes it easier to reason about elements kinds, and less confusing to explain how they’re used. R=jkummerow@chromium.org, cbruni@chromium.org BUG=v8:6548 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: Ie7c6bee85583c3d84b730f7aebbd70c1efa38af9 Reviewed-on: https://chromium-review.googlesource.com/556032Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Mathias Bynens <mathias@chromium.org> Cr-Commit-Position: refs/heads/master@{#46361}
-
- 09 Jun, 2017 1 commit
-
-
Igor Sheludko authored
Use convenient macros for accessing bit fields. Bug: v8:6470 Change-Id: Iada9779ce56c7ca2e8b6a9617c236e294db7325e Reviewed-on: https://chromium-review.googlesource.com/527432 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#45804}
-
- 17 May, 2017 1 commit
-
-
Marja Hölttä authored
Previous version was https://chromium-review.googlesource.com/502808 BUG=v8:5402 Change-Id: If327f4d7884577b7e5e6159372bf28a80cd21e51 Reviewed-on: https://chromium-review.googlesource.com/506073 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#45369}
-
- 15 May, 2017 2 commits
-
-
Marja Hölttä authored
This reverts commit 7be0159e. Reason for revert: Broke node by generating a broken debug-support.cc Original change's description: > [objects.h splitting] Move Map and related classes. > > BUG=v8:5402 > > Change-Id: I64fae0a0271eb0f1b71f4ec5d9bd5d22deb1cf59 > Reviewed-on: https://chromium-review.googlesource.com/502808 > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Reviewed-by: Igor Sheludko <ishell@chromium.org> > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> > Commit-Queue: Marja Hölttä <marja@chromium.org> > Cr-Commit-Position: refs/heads/master@{#45305} TBR=marja@chromium.org,mstarzinger@chromium.org,jarin@chromium.org,ishell@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:5402 Change-Id: Ifa65537447eb0a1ef947b9d0dae6f07a8b150968 Reviewed-on: https://chromium-review.googlesource.com/506011Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/master@{#45307}
-
Marja Hölttä authored
BUG=v8:5402 Change-Id: I64fae0a0271eb0f1b71f4ec5d9bd5d22deb1cf59 Reviewed-on: https://chromium-review.googlesource.com/502808Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/master@{#45305}
-
- 26 Apr, 2017 1 commit
-
-
info authored
Add PropertyDetails::AttributesField + PropertyDetails::LocationField. Review-Url: https://codereview.chromium.org/2842843004 Cr-Commit-Position: refs/heads/master@{#44889}
-
- 25 Apr, 2017 1 commit
-
-
Marja Hölttä authored
The data produced by the preparser scope analysis might be large. ByteArrays are already allowed in the large object space. This fixes mjsunit/asm/poppler/poppler.js with the flag on. First version landed as https://chromium-review.googlesource.com/c/484459/ this version includes gen-postmortem-metadata fixes. BUG=v8:5516 Change-Id: I2218c4729ba9feefd6595a93e5cc6d2e52ebda0e Reviewed-on: https://chromium-review.googlesource.com/486641Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/master@{#44835}
-
- 09 Feb, 2017 1 commit
-
-
jkummerow authored
DescriptorArray::kDescriptorFoo was renamed to DescriptorArray::kEntryFooIndex in https://codereview.chromium.org/2688573003 TBR=ishell@chromium.org NOTRY=true Review-Url: https://codereview.chromium.org/2687083003 Cr-Commit-Position: refs/heads/master@{#43076}
-
- 27 Jan, 2017 1 commit
-
-
julien.gilli authored
Previously (and still currently for some of them), post-mortem debugging tools were using StandardFrameConstants::kContextOffset as the offset to get the value that represents a frame's type. However since https://codereview.chromium.org/1696043002, a new, more general offset was introduced: CommonFrameConstants::kContextOrFrameTypeOffset. In order for post-mortem debugging tools to use this constant, it is included in the generated post-mortem metadata. R=danno@chromium.org,bmeurer@chromium.org BUG= Review-Url: https://codereview.chromium.org/2655553006 Cr-Commit-Position: refs/heads/master@{#42746}
-
- 16 Jan, 2017 2 commits
-
-
ishell authored
NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review-Url: https://codereview.chromium.org/2636893002 Cr-Commit-Position: refs/heads/master@{#42376}
-
franzih authored
Remove now obsolete constants (see https://chromium.googlesource.com/v8/v8/+/8f0bf07b504e8bb27ef3703388c4c0699670331f) from postmortem metadata generator. BUG= Review-Url: https://codereview.chromium.org/2636863004 Cr-Commit-Position: refs/heads/master@{#42374}
-
- 21 Nov, 2016 1 commit
-
-
fedor authored
Export JS_API_OBJECT_TYPE, JS_SPECIAL_API_OBJECT_TYPE. Exports JSObject::kHeaderSize to ease the inspection of internal fields in llnode. BUG= R=machenbach Review-Url: https://codereview.chromium.org/2514063002 Cr-Commit-Position: refs/heads/master@{#41157}
-
- 29 Aug, 2016 1 commit
-
-
verwaest authored
This additionally gets rid of old approach to global shortcuts. BUG=v8:5209 Review-Url: https://codereview.chromium.org/2287173002 Cr-Commit-Position: refs/heads/master@{#38980}
-
- 29 Jun, 2016 1 commit
-
-
ishell authored
This CL changed layout of UnseededNumberDictionary: https://codereview.chromium.org/2102073002. Review-Url: https://codereview.chromium.org/2105553006 Cr-Commit-Position: refs/heads/master@{#37398}
-
- 10 Jun, 2016 1 commit
-
-
julien.gilli authored
Some post-mortem metadata constants that are not offsets to objects' properties were incorrectly defined in the accessors table. This change fixes it by moving them from the accessors table to the constants table. More background is available at https://github.com/nodejs/post-mortem/issues/27. R=danno@chromium.org,bmeurer@chromium.org BUG= Review-Url: https://codereview.chromium.org/2051563003 Cr-Commit-Position: refs/heads/master@{#36878}
-
- 27 Apr, 2016 1 commit
-
-
fedor authored
Useful for inspecting constant fields in objects. BUG= R=machenbach Review-Url: https://codereview.chromium.org/1922903003 Cr-Commit-Position: refs/heads/master@{#35826}
-
- 11 Mar, 2016 1 commit
-
-
ofrobots authored
Post-mortem metadata generation broke as a result of https://codereview.chromium.org/1696043002 BUG= Review URL: https://codereview.chromium.org/1780933004 Cr-Commit-Position: refs/heads/master@{#34725}
-
- 22 Feb, 2016 1 commit
-
-
ben authored
BUG= Review URL: https://codereview.chromium.org/1718953002 Cr-Commit-Position: refs/heads/master@{#34186}
-
- 22 Dec, 2015 1 commit
-
-
ofrobots authored
Context::GLOBAL_OBJECT_INDEX has been replaced by NATIVE_CONTEXT_INDEX in https://codereview.chromium.org/1480003002. Update the postmortem data generator to reflect this change. R=bmeurer@chromium.org,yangguo@chromium.org BUG= Review URL: https://codereview.chromium.org/1542753002 Cr-Commit-Position: refs/heads/master@{#32993}
-
- 30 Nov, 2015 1 commit
-
-
thechargingvolcano authored
In Python, `strip` can be used directly instead of stripping the ends one by one. R=machenbach@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1443963004 Cr-Commit-Position: refs/heads/master@{#32413}
-
- 12 Nov, 2015 2 commits
-
-
evan.lucas authored
Instead of basing matches off of whitespace, walk the inheritance chain and include any classes that inherit from Object. R=machenbach@chromium.org,jkummerow@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1435643002 Cr-Commit-Position: refs/heads/master@{#31964}
-
fedor authored
BUG= R=machenbach Review URL: https://codereview.chromium.org/1439763002 Cr-Commit-Position: refs/heads/master@{#31961}
-
- 11 Nov, 2015 1 commit
-
-
fedor authored
I have discovered need in those values when writing: https://github.com/indutny/llnode BUG= Review URL: https://codereview.chromium.org/1436473002 Cr-Commit-Position: refs/heads/master@{#31947}
-
- 25 Sep, 2015 1 commit
-
-
julien.gilli authored
mdb_v8, a post-mortem debugger for Node.js, now uses JSArrayBuffer's backing_store property and JSArrayBufferView's byte_offset property to get access to the content of Buffer instances in node (which are Uint8Array instances). This change adds post-mortem metadata for these two properties. This change also fixes a typo in inobject_properties_of_constructor_function_index_offset that was added to gen-postmortem-metadata in a previous change. It should be named inobject_properties_or_constructor_function_index instead. R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1363403003 Cr-Commit-Position: refs/heads/master@{#30926}
-
- 23 Sep, 2015 1 commit
-
-
julien.gilli authored
BUG= R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1363683002 Cr-Commit-Position: refs/heads/master@{#30873}
-
- 21 Sep, 2015 1 commit
-
-
julien.gilli authored
mdb_v8, a post-mortem debugging tool for Node.js, allows users to inspect ScopeInfo structures in order to get more information about closures. Currently, it hardcodes the metadata it uses to find this information. This change allows it to get this metadata from the node binary itself, and thus to adapt to future changes made to the layout of the ScopeInfo data structure. BUG= R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1350843003 Cr-Commit-Position: refs/heads/master@{#30843}
-
- 18 Sep, 2015 1 commit
-
-
julien.gilli authored
Since https://codereview.chromium.org/272163002, BitField3 is a raw uint32 field, and not a SMI anymore. Update tools/gen-postmortem-metadata.py so that post-mortem tools can work with versions of V8 that shipped after that change. This change was merged in github.com/joyent/node right before node v0.12.0 was released. R=danno@chromium.org TEST=mdb_v8, a post-mortem debugging tool running on SmartOS, has been using this change since Node.js v0.12.0 was released BUG= Review URL: https://codereview.chromium.org/1296743003 Cr-Commit-Position: refs/heads/master@{#30839}
-
- 02 Sep, 2015 1 commit
-
-
ofrobots authored
This is causing build breaks for Node.js w/ V8 4.6. Map::kInObjectPropertiesOffset was been replaced by kInObjectPropertiesOrConstructorFunctionIndexOffset in https://codereview.chromium.org/1276533003. This is causing the post-mortem debug information generation to fail. R=bmeurer@chromium.org BUG= Review URL: https://codereview.chromium.org/1308113007 Cr-Commit-Position: refs/heads/master@{#30536}
-
- 25 Mar, 2015 1 commit
-
-
fedor authored
This commit has changed the enum names: 33994b4a `FIELD` is now called `DATA`. BUG= R=danno Review URL: https://codereview.chromium.org/1033733003 Cr-Commit-Position: refs/heads/master@{#27434}
-
- 02 Feb, 2015 1 commit
-
-
fedor authored
BUG= R=danno Review URL: https://codereview.chromium.org/892223002 Cr-Commit-Position: refs/heads/master@{#26389}
-
- 10 Sep, 2014 1 commit
-
-
yangguo@chromium.org authored
TBR=marja@chromium.org Review URL: https://codereview.chromium.org/561743002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23841 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 23 Jul, 2014 1 commit
-
-
danno@chromium.org authored
Expose more info about post-mortem constants Useful for node.js and/or other tools. BUG= R=danno@chromium.org Review URL: https://codereview.chromium.org/404173002 Patch from Fedor Indutny <fedor.indutny@gmail.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22549 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 02 Apr, 2014 1 commit
-
-
jkummerow@chromium.org authored
R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/221513002 Patch from Ben Noordhuis <ben@strongloop.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@20436 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 30 Dec, 2013 1 commit
-
-
rmcilroy@chromium.org authored
Third stage of implementing an out-of-line constant pool for Arm. This CL adds a ConstantPool field to Code objects and initializes the pp register on function entry, and saves the pp register on the stack frame. The ConstantPool object is always empty and is unused currently. R=ulan@chromium.org Review URL: https://codereview.chromium.org/88043002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@18425 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 14 Oct, 2013 1 commit
-
-
jkummerow@chromium.org authored
strings, sliced strings, and changes to some object property representations. R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/26034002 Patch from David Pacheco <dap@joyent.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17194 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 03 Jan, 2013 1 commit
-
-
svenpanne@chromium.org authored
Review URL: https://codereview.chromium.org/11744019 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@13303 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 28 Dec, 2012 1 commit
-
-
danno@chromium.org authored
Right now it's impossible to figure out from headers that smis are left shifted by 31 bit on x64, and only then tagged. R=erik.corry@gmail.com Review URL: https://codereview.chromium.org/11676005 Patch from Fedor Indutny <fedor@indutny.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@13285 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-