Blink-compatible serialization of strings.
This includes UTF-8 strings and two-byte strings, both length-delimited
(in bytes, not characters). Two-byte strings are written/read in host byte
order.
BUG=chromium:148757
Committed: https://crrev.com/c5701e166ed3eee6f731ff1ec8ccac3c8ff85192
Cr-Commit-Position: refs/heads/master@{#38636}
https://codereview.chromium.org/2245753002/diff/80001/src/value-serializer.cc File src/value-serializer.cc (right): https://codereview.chromium.org/2245753002/diff/80001/src/value-serializer.cc#newcode202 src/value-serializer.cc:202: uint32_t utf8_length = api_string->Utf8Length(); On 2016/08/14 at 15:10:48, Camillo ...
4 years, 4 months ago
(2016-08-15 01:33:52 UTC)
#4
https://codereview.chromium.org/2245753002/diff/80001/src/value-serializer.cc
File src/value-serializer.cc (right):
https://codereview.chromium.org/2245753002/diff/80001/src/value-serializer.cc...
src/value-serializer.cc:202: uint32_t utf8_length = api_string->Utf8Length();
On 2016/08/14 at 15:10:48, Camillo Bruni wrote:
> performance nit: I'd prefer not wrapping the Handle<String> into a Local.
Funily enough, all the API functions (Utf8Length and WriteUtf8) use the a
Handle<String> internally. So at some point you can just provide the
Handle<String>-based helper separately.
Agreed that wrapping in a Local<> isn't great. Ideally I'd like to add a new tag
for one-byte strings and then stop writing out UTF-8 altogether (decoding it
would still be required, but that doesn't have to use a Local<>). If that
doesn't come together, then that refactor sounds reasonable to me.
jbroman
The CQ bit was checked by jbroman@chromium.org to run a CQ dry run
4 years, 4 months ago
(2016-08-15 01:33:58 UTC)
#5
Dry run: Try jobs failed on following builders: v8_win_compile_dbg on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_win_compile_dbg/builds/22573) v8_win_rel_ng on ...
4 years, 4 months ago
(2016-08-15 01:37:58 UTC)
#8
4 years, 4 months ago
(2016-08-15 15:26:45 UTC)
#15
Message was sent while issue was closed.
Committed patchset #7 (id:120001)
commit-bot: I haz the power
Description was changed from ========== Blink-compatible serialization of strings. This includes UTF-8 strings and two-byte ...
4 years, 4 months ago
(2016-08-15 15:27:17 UTC)
#16
Message was sent while issue was closed.
Description was changed from
==========
Blink-compatible serialization of strings.
This includes UTF-8 strings and two-byte strings, both length-delimited
(in bytes, not characters). Two-byte strings are written/read in host byte
order.
BUG=chromium:148757
==========
to
==========
Blink-compatible serialization of strings.
This includes UTF-8 strings and two-byte strings, both length-delimited
(in bytes, not characters). Two-byte strings are written/read in host byte
order.
BUG=chromium:148757
Committed: https://crrev.com/c5701e166ed3eee6f731ff1ec8ccac3c8ff85192
Cr-Commit-Position: refs/heads/master@{#38636}
==========
commit-bot: I haz the power
Patchset 7 (id:??) landed as https://crrev.com/c5701e166ed3eee6f731ff1ec8ccac3c8ff85192 Cr-Commit-Position: refs/heads/master@{#38636}
4 years, 4 months ago
(2016-08-15 15:27:18 UTC)
#17
Issue 2245753002: Blink-compatible serialization of strings.
(Closed)
Created 4 years, 4 months ago by jbroman
Modified 4 years, 4 months ago
Reviewers: Camillo Bruni
Base URL: https://chromium.googlesource.com/v8/v8.git@vs2
Comments: 2