00:00:51  * plutoniixquit (Quit: Leaving)
00:59:21  * scottmg_changed nick to scottmg
01:30:38  * xaxxonquit (Ping timeout: 244 seconds)
01:45:15  * plutoniixjoined
01:45:22  * plutoniixquit (Max SendQ exceeded)
01:45:54  * plutoniixjoined
02:14:24  * zvquit (Quit: WeeChat 1.5)
02:42:40  * bradleymeckjoined
02:45:33  * plutoniixquit (Ping timeout: 260 seconds)
03:28:08  <caitp>all the AssertGeneratorObject() stuff is making it really hard to re-use existing generator trampoline codestubs
03:41:02  * bradleymeckquit (Quit: bradleymeck)
05:13:32  * xaxxonjoined
05:13:55  * plutoniixjoined
08:25:31  * Keverwjoined
09:32:10  * xaxxonquit (Quit: Leaving)
10:34:55  * hferreirojoined
11:29:16  * plutoniixquit (Quit: Leaving)
11:45:36  * Keverwquit (Quit: Textual IRC Client: www.textualapp.com)
13:32:58  * sxaquit (Ping timeout: 265 seconds)
13:38:49  * sxajoined
14:19:26  * bradleymeckjoined
14:24:33  * xaxxonjoined
15:33:37  * bradleymeckquit (Quit: bradleymeck)
15:50:22  * plutoniixjoined
15:50:32  * plutoniixquit (Max SendQ exceeded)
15:51:07  * plutoniixjoined
16:00:19  * sxaquit (Read error: Connection reset by peer)
16:02:08  * sxajoined
16:07:56  * throsturjoined
16:16:44  <caitp>something I'm realizing with the aligned backslashes in macrodefinitions (eg in runtime.h and builtins.h) is, it really sucks resolving merge conflicts with those
16:17:07  <caitp>maybe the aesthetics of it aren't worth it
16:18:25  <caitp>plus it makes git blame kind of useless
16:25:16  <gsathya>+1
16:26:05  <gsathya>do not like alphasorting also
16:32:13  * RT|Chatzillaquit (Quit: ChatZilla 0.9.86.1 [Firefox 2.0.0.22pre/2010030309])
16:36:34  * bradleymeckjoined
16:58:42  * bradleymeckquit (Quit: bradleymeck)
16:59:20  * xaxxonquit (Quit: Leaving)
17:07:55  <trungl-bot`>Tree closed by buildbot@chromium.org: Tree is closed (Automatic: "Mjsunit" on http://build.chromium.org/p/client.v8/builders/V8%20Mac%20GC%20Stress/builds/10259 "V8 Mac GC Stress" from 94cd46b55e24fa2bb7b06b3da4d5ba7f029bc262: clemensh@chromium.org)
17:09:12  * bradleymeckjoined
17:10:30  * hferreiroquit (Quit: Connection closed for inactivity)
17:54:21  <jwolfe>should https://bugs.chromium.org/p/v8/issues/detail?id=4973 stay open, or be closed? the only reason i can think of to keep it open is if we wanted to revert the potentially breaking change.
17:55:29  <caitp>jwolfe: I think you can call it fixed
17:56:04  <caitp>if new info comes along, you can reopen it or just migrate to the new bug that gets opened
17:56:14  <caitp>which from experience will probably be on the chromium tracker
17:57:09  <jwolfe>should i also remove labels Hotlist-test262 and SpecViolation-OpenQuestion?
17:57:35  <caitp>I don't see any reason to
17:57:44  <caitp>if you want, I guess
17:58:02  <caitp>they won't affect filtered searches which only look for open issues, which I expect most people use
18:01:32  * decoderquit (Ping timeout: 268 seconds)
18:03:57  * decoderjoined
18:20:24  <aklein>jwolfe: please don't remove labels upon closing
18:20:39  <aklein>they're useful for keeping track of stats like "how many specviolation-openquestion bugs did we close this quarter?"
18:22:25  <jwolfe>aklein, got it.
18:22:30  <trungl-bot`>Tree opened by buildbot@chromium.org: Tree is open (Automatic: Uve nemhanza yakanaka)
18:23:58  <aklein>jwolfe: and thanks for closing the bug! generally as soon as the bug is taken care of, it's marked as fixed. it might get reopened if the change ends up getting rolled back in the future.
18:26:41  <jwolfe>aklein, good to know.
18:28:19  <aklein>that tracking is most important for regression bugs, since they need to be marked "fixed" before they can be considered for merging to a release branch
18:34:35  * zvjoined
19:07:35  * bradleymeckquit (Quit: bradleymeck)
19:08:52  * bradleymeckjoined
19:21:59  <trungl-bot`>Tree closed by buildbot@chromium.org: Tree is closed (Automatic: "generate_build_files" on http://build.chromium.org/p/client.v8.ports/builders/V8%20Arm%20-%20debug%20builder/builds/4734 "V8 Arm - debug builder" from 43e7d05125e9356ce7d6fc504ba30c325521d383: mtrofin@chromium.org)
19:24:00  <trungl-bot`>Tree opened by mtrofin@chromium.org: open
20:20:29  * hferreirojoined
20:56:19  * bradleymeckquit (Quit: bradleymeck)
20:59:28  * bradleymeckjoined
21:04:21  * xaxxonjoined
21:09:33  <caitp>so CodeAssembler::CallStub() has a result_size parameter, but no stubs actually use a result_size != 1
21:09:53  <caitp>at least, that I can see
21:09:53  <caitp>and there also doesn't seem to be test coverage for non-1 result sizes
21:10:18  <caitp>if you use a non-1 result size, it seems to interact very poorly with the register allocator
21:48:03  * xaxxonquit (Quit: Leaving)
22:13:24  * bradleymeckquit (Quit: bradleymeck)
22:13:33  * xaxxonjoined
22:16:00  * xaxxonpart
22:32:24  * bradleymeckjoined
22:53:36  * RT|Chatzillajoined
22:59:37  * plutoniixquit (Quit: Leaving)
23:13:57  * bradleymeckquit (Quit: bradleymeck)
23:31:54  <trungl-bot`>Tree closed by buildbot@chromium.org: Tree is closed (Automatic: "gclient runhooks" on http://build.chromium.org/p/client.v8/builders/V8%20Linux%20ASAN%20mipsel%20-%20debug%20builder/builds/12104 "V8 Linux ASAN mipsel - debug builder" from bb309a6998a44f698626819c5c87c8feb9a2162a: neis@chromium.org)
23:56:51  * Guest59quit (Read error: Connection reset by peer)
23:57:13  * Guest59joined