00:08:40  * watildequit (Remote host closed the connection)
00:34:46  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
00:35:12  * plutoniixjoined
00:35:24  * plutoniixquit (Max SendQ exceeded)
00:36:04  * plutoniixjoined
00:50:29  * watildejoined
00:55:24  * watildequit (Ping timeout: 258 seconds)
01:26:42  * unixpicklejoined
01:27:02  * xaxxonquit (Read error: Connection reset by peer)
01:27:55  * xaxxonjoined
01:34:38  * bradleymeckquit (Quit: bradleymeck)
01:44:54  * watildejoined
01:49:50  * watildequit (Ping timeout: 258 seconds)
02:27:37  * Vbitzquit (Ping timeout: 240 seconds)
02:33:16  * Vbitzjoined
02:56:29  * bradleymeckjoined
03:12:57  * battousaiquit (Ping timeout: 240 seconds)
03:13:37  * toddynhoquit (Ping timeout: 240 seconds)
03:17:45  * battousaijoined
03:18:20  * toddynhojoined
03:33:18  * watildejoined
03:37:41  * watildequit (Ping timeout: 252 seconds)
03:40:29  <ayjay_t>meh i'm trying to follow the embedders guide to get an idea of how big a minimal v8 set of binaries is but it breaks on ninja
03:41:22  <ayjay_t>lots of subcommand failures, failures in general. no libtinfo.so.5 which it seems to survive, then there was a js2c failure so i installed js2coffee via npm, got past that, now it's stopping on postmortem-metadata
03:42:03  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
03:56:52  * bradleymeckquit (Quit: bradleymeck)
04:17:46  * unixpicklejoined
04:27:08  * watildejoined
04:31:30  * watildequit (Ping timeout: 255 seconds)
04:44:03  * xaxxonquit (Quit: Leaving)
05:08:37  * toddynhoquit (Ping timeout: 240 seconds)
05:10:37  * battousaiquit (Ping timeout: 240 seconds)
05:11:31  * toddynhojoined
05:12:46  * battousaijoined
05:21:13  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
05:21:16  * watildejoined
05:26:08  * watildequit (Ping timeout: 260 seconds)
06:33:15  * jochen___changed nick to jochen__
06:40:04  * s1341joined
07:09:26  * watildejoined
07:13:57  * watildequit (Ping timeout: 240 seconds)
08:02:53  * bradleymeckjoined
08:03:29  * watildejoined
08:07:27  * bradleymeckquit (Ping timeout: 240 seconds)
08:08:24  * watildequit (Ping timeout: 255 seconds)
08:30:26  * plutoniixquit (Ping timeout: 260 seconds)
08:42:30  * plutoniixjoined
08:43:25  * plutoniixquit (Max SendQ exceeded)
08:43:52  * plutoniixjoined
08:44:54  * plutoniixquit (Max SendQ exceeded)
08:45:22  * plutoniixjoined
09:51:48  * watildejoined
09:56:20  * watildequit (Ping timeout: 260 seconds)
09:58:13  * plutoniixquit (Read error: Connection reset by peer)
10:24:18  * bradleymeckjoined
10:25:05  * mylesborinsquit (Quit: farewell for now)
10:25:36  * mylesborinsjoined
10:29:00  * bradleymeckquit (Ping timeout: 260 seconds)
10:46:02  * watildejoined
10:50:10  * watildequit (Ping timeout: 240 seconds)
11:27:10  * Tweth-U-PDSjoined
11:27:34  * Garbeequit (Quit: ZNC 1.6.3+deb1+xenial0 - http://znc.in)
11:29:35  * Tweth-V-PDSquit (Ping timeout: 252 seconds)
11:32:53  * ayjay_tquit (Ping timeout: 252 seconds)
11:32:58  * Garbeejoined
11:33:22  * Garbeechanged nick to Guest19446
11:34:19  * ayjay_tjoined
11:39:49  * watildejoined
11:42:18  * Guest19446quit (Quit: ZNC 1.6.3+deb1+xenial0 - http://znc.in)
11:44:10  * watildequit (Ping timeout: 240 seconds)
12:25:03  * bradleymeckjoined
12:29:23  * bradleymeckquit (Ping timeout: 245 seconds)
12:31:40  * Garbeejoined
12:32:04  * Garbeechanged nick to Guest11079
12:34:05  * watildejoined
12:38:28  * watildequit (Ping timeout: 255 seconds)
12:39:27  * Guest11079changed nick to Garbee
12:49:55  * bradleymeckjoined
13:25:49  * plutoniixjoined
13:28:15  * watildejoined
13:29:50  * bradleymeckquit (Quit: bradleymeck)
13:32:51  * watildequit (Ping timeout: 255 seconds)
13:50:42  * bradleymeckjoined
13:59:30  * unixpicklejoined
14:06:02  * plutoniixquit (Quit: Leaving)
14:08:52  * plutoniixjoined
14:14:28  <s1341>are the older IC handlers (i.e. not the data-driven ones which use the feedback vector) used anymore in the new pipeline?
14:14:34  <s1341>caitp: ^^
14:15:06  <caitp>I am totally not the expert on the IC subsystem
14:15:17  <caitp>I'd have to do a lot of research before getting back to you on that
14:15:24  <s1341>caitp: can you point me in the direction of the person to ask?
14:15:40  <s1341>I'm just trying to figure out if this code is even active at this stage...
14:16:06  <caitp>check src/ic/OWNERS
14:16:39  <caitp>I think jummerow answers questions like this on [email protected] sometimes
14:16:48  <caitp>jkummerow*
14:17:08  <s1341>ok. i prefer IRC to mailing lists...
14:17:54  <caitp>how about twitter? You might be able to get a quick-ish answer from Benedikt about it there
14:18:49  <s1341>caitp: twitter works ;)
14:18:55  <s1341>do you have a handle for Benedikt?
14:19:40  <caitp>@bmeurer
14:20:27  <caitp>dunno if the other owners are active on twitter or not, good luck
14:21:20  <s1341>thanks. Seems like a good person to follow ;)
14:22:13  * watildejoined
14:22:32  <s1341>caitp: sorry i picked on you... just historically had good luck getting info from you ;)
14:22:41  <s1341>the price of wisdom, i guess ;)
14:23:08  <caitp>well hopefully some day I can learn more about how the IC system works with the various backends. I only have a rough idea, since the work I do usually doesn't involve IC ata ll
14:26:28  * watildequit (Ping timeout: 245 seconds)
14:31:27  <s1341>caitp what type of work do you do?
14:33:10  <caitp>I work for a consultancy, mostly on implementing language features and investigating embedder performance in v8 and JSC
14:37:25  <s1341>ok.
14:37:38  <s1341>so which bits of the codebase do you generally touch?
14:39:34  <caitp>src/builtins/*, src/parsing/*, src/runtime/*, src/interpreter/*, the bootstrapper and core objects files, occasionally src/compiler/* and src/heap/*
14:39:53  <s1341>i see. that's quite a wide path in the code ;)
14:40:09  <s1341>but now I have a better idea which questions to direct your way ;)
14:40:27  <s1341>do you know anything about map tranisitions?
14:40:37  <trungl-bot>Tree closed by [email protected]: closed (/builders/V8%20Win64/builds/17063 from 245ab01ad46d0ac5cf307049a9ba5bd2b6b2f0a4)
14:41:41  <caitp>I know a bit about them
14:42:40  <trungl-bot>Tree opened by [email protected]: open
15:01:01  <s1341>caitp: ok. i'm confused about properties and map transitions.
15:01:45  <s1341>where are properties actually stored? it seems that the properties pointer (+4) is pointing to an empty FixedArray even after I've added some properties to my object.
15:16:28  * watildejoined
15:21:08  * watildequit (Ping timeout: 260 seconds)
15:22:15  <caitp>> where are properties actually stored?
15:22:18  <caitp>answer: it depends
15:22:30  <s1341>...?
15:25:04  <caitp>there are in-object fields, in-map properties, element properties
15:25:58  <s1341>caitp is there any documentation for this that I could read instead of pestering you?
15:30:33  <caitp>it's not something that the embedder or user is really supposed to care about
15:30:48  <caitp>so the only real documentation is reading the code
15:30:55  <caitp>and of course it can change at any time
15:37:30  <s1341>yay.
15:46:27  * RT|Chatzillaquit (Quit: ChatZilla 0.9.86.1 [Firefox 2.0.0.22pre/2010030309])
16:09:16  * plutoniixquit (Ping timeout: 258 seconds)
16:10:20  * watildejoined
16:14:35  * watildequit (Ping timeout: 240 seconds)
16:22:09  * plutoniixjoined
16:39:39  * plutoniixquit (Read error: Connection reset by peer)
16:45:30  * seventhjoined
17:00:22  * plutoniixjoined
17:11:57  * toddynhoquit (Ping timeout: 240 seconds)
17:12:37  * battousaiquit (Ping timeout: 240 seconds)
17:16:38  * battousaijoined
17:16:44  * toddynhojoined
17:44:52  * Guest59_joined
17:47:26  * Guest59quit (Ping timeout: 252 seconds)
17:49:15  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
17:50:36  * s1341quit (Quit: Connection closed for inactivity)
18:12:37  * battousaiquit (Ping timeout: 240 seconds)
18:14:37  * toddynhoquit (Ping timeout: 240 seconds)
18:16:31  * battousaijoined
18:16:31  * toddynhojoined
18:20:33  * seventhquit (Quit: ...)
18:23:38  <jwolfe>today i learned, you can't use await at top-level scope. and it's a SyntaxError. so checking to see if you have async/await support is pretty confusing if you quickly try `await foo();` to see what error message you get XS
18:36:04  * seventhjoined
18:37:46  * unixpicklejoined
18:40:37  * unixpicklequit (Client Quit)
18:41:06  * unixpicklejoined
18:51:54  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
18:52:32  * watildejoined
18:53:18  <caitp>jwolfe: I think it's supposed to be allowed at top-level in modules
18:53:31  <caitp>or at least, in the future
18:57:30  * watildequit (Ping timeout: 260 seconds)
19:29:44  * unixpicklejoined
19:45:35  * ayjay_tquit (Read error: Connection reset by peer)
19:46:03  * ayjay_tjoined
19:46:40  * watildejoined
19:51:03  <jwolfe>as a clarification to my previous claim, it's more generally anytime you use await outside an async function, then it's a SyntaxError, as though there were no such thing as the await feature. so it makes sense that top-level scop is not async.
19:53:42  * watildequit (Ping timeout: 240 seconds)
19:57:25  * seventhquit (Remote host closed the connection)
20:35:06  * Guest59_quit (Quit: My Mac has gone to sleep. ZZZzzz…)
20:36:04  * Guest59joined
20:37:17  * toddynhoquit (Ping timeout: 240 seconds)
20:38:17  * battousaiquit (Ping timeout: 240 seconds)
20:42:02  * toddynhojoined
20:44:02  * battousaijoined
20:44:48  * battousaiquit (Max SendQ exceeded)
20:46:59  * battousaijoined
21:55:20  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
22:21:22  * watildejoined
22:42:40  * RT|Chatzillajoined
22:51:51  * plutoniixquit (Quit: Leaving)
23:31:39  * unixpicklejoined
23:32:17  * battousaiquit (Ping timeout: 240 seconds)
23:32:17  * toddynhoquit (Ping timeout: 240 seconds)
23:37:09  * battousaijoined
23:37:09  * toddynhojoined
23:53:14  <trungl-bot>Tree closed by [email protected]: closed (/builders/V8%20Linux%20-%20arm64%20-%20sim%20-%20nosnap%20-%20debug/builds/4534 from cd76322817760cd1c1d7538f51f1907df7b6cde3)
23:54:43  * watildequit (Remote host closed the connection)