WEBVTT Kind: captions Language: en 00:00:00.210 --> 00:00:20.130 align:start position:0% [Music] 00:00:20.130 --> 00:00:20.140 align:start position:0% 00:00:20.140 --> 00:00:23.410 align:start position:0% hello<00:00:21.170> they're<00:00:21.860> subjecting<00:00:22.580> me<00:00:22.850> to<00:00:22.880> this 00:00:23.410 --> 00:00:23.420 align:start position:0% hello they're subjecting me to this 00:00:23.420 --> 00:00:26.040 align:start position:0% hello they're subjecting me to this again<00:00:24.250> and 00:00:26.040 --> 00:00:26.050 align:start position:0% again and 00:00:26.050 --> 00:00:28.630 align:start position:0% again and the<00:00:27.050> title<00:00:27.680> was<00:00:27.950> supposed<00:00:28.340> to<00:00:28.430> be<00:00:28.610> a 00:00:28.630 --> 00:00:28.640 align:start position:0% the title was supposed to be a 00:00:28.640 --> 00:00:31.810 align:start position:0% the title was supposed to be a placeholder<00:00:29.000> but<00:00:29.750> George<00:00:30.140> he<00:00:31.130> liked<00:00:31.369> it<00:00:31.579> so 00:00:31.810 --> 00:00:31.820 align:start position:0% placeholder but George he liked it so 00:00:31.820 --> 00:00:35.040 align:start position:0% placeholder but George he liked it so much<00:00:31.880> he<00:00:32.480> made<00:00:33.230> me<00:00:33.560> keep<00:00:33.740> it 00:00:35.040 --> 00:00:35.050 align:start position:0% much he made me keep it 00:00:35.050 --> 00:00:38.200 align:start position:0% much he made me keep it louder<00:00:36.050> louder<00:00:36.620> I<00:00:37.130> was<00:00:37.640> supposed<00:00:37.970> to<00:00:38.030> have<00:00:38.150> a 00:00:38.200 --> 00:00:38.210 align:start position:0% louder louder I was supposed to have a 00:00:38.210 --> 00:00:40.420 align:start position:0% louder louder I was supposed to have a headset<00:00:38.480> too<00:00:39.050> so<00:00:39.320> I<00:00:39.380> didn't<00:00:39.650> have<00:00:39.739> to<00:00:39.920> do<00:00:40.100> this 00:00:40.420 --> 00:00:40.430 align:start position:0% headset too so I didn't have to do this 00:00:40.430 --> 00:00:42.540 align:start position:0% headset too so I didn't have to do this but<00:00:41.180> here<00:00:41.600> we<00:00:41.750> are 00:00:42.540 --> 00:00:42.550 align:start position:0% but here we are 00:00:42.550 --> 00:00:46.000 align:start position:0% but here we are my<00:00:43.550> job<00:00:43.970> when<00:00:44.300> I<00:00:44.329> got<00:00:44.720> here<00:00:45.079> was<00:00:45.320> to<00:00:45.560> take<00:00:45.800> this 00:00:46.000 --> 00:00:46.010 align:start position:0% my job when I got here was to take this 00:00:46.010 --> 00:00:49.990 align:start position:0% my job when I got here was to take this interpreter<00:00:47.000> and<00:00:47.210> make<00:00:47.930> it<00:00:48.140> go<00:00:48.760> faster<00:00:49.760> I 00:00:49.990 --> 00:00:50.000 align:start position:0% interpreter and make it go faster I 00:00:50.000 --> 00:00:52.870 align:start position:0% interpreter and make it go faster I wanted<00:00:50.960> to<00:00:51.080> make<00:00:51.230> it<00:00:51.410> scream<00:00:51.830> like<00:00:52.280> this<00:00:52.340> this 00:00:52.870 --> 00:00:52.880 align:start position:0% wanted to make it scream like this this 00:00:52.880 --> 00:00:54.880 align:start position:0% wanted to make it scream like this this was<00:00:53.060> exactly<00:00:53.390> the<00:00:53.810> image<00:00:54.110> I<00:00:54.260> had<00:00:54.440> in<00:00:54.470> mind 00:00:54.880 --> 00:00:54.890 align:start position:0% was exactly the image I had in mind 00:00:54.890 --> 00:00:57.340 align:start position:0% was exactly the image I had in mind there<00:00:55.520> was<00:00:55.580> a<00:00:55.640> kid<00:00:55.910> in<00:00:56.030> junior<00:00:56.360> high<00:00:56.570> r2<00:00:57.080> just 00:00:57.340 --> 00:00:57.350 align:start position:0% there was a kid in junior high r2 just 00:00:57.350 --> 00:00:59.410 align:start position:0% there was a kid in junior high r2 just drew<00:00:57.560> pictures<00:00:57.800> like<00:00:58.190> this<00:00:58.400> over<00:00:58.850> and<00:00:59.000> over<00:00:59.240> I 00:00:59.410 --> 00:00:59.420 align:start position:0% drew pictures like this over and over I 00:00:59.420 --> 00:01:02.880 align:start position:0% drew pictures like this over and over I love<00:00:59.690> them<00:00:59.960> the<00:01:00.650> art<00:01:00.800> teacher<00:01:00.860> didn't<00:01:01.720> and 00:01:02.880 --> 00:01:02.890 align:start position:0% love them the art teacher didn't and 00:01:02.890 --> 00:01:05.649 align:start position:0% love them the art teacher didn't and there's<00:01:03.890> a<00:01:03.950> little<00:01:04.159> video<00:01:04.369> you<00:01:04.580> can<00:01:04.939> play<00:01:05.180> here 00:01:05.649 --> 00:01:05.659 align:start position:0% there's a little video you can play here 00:01:05.659 --> 00:01:07.330 align:start position:0% there's a little video you can play here this<00:01:05.990> is<00:01:06.170> the<00:01:06.380> chip<00:01:06.650> that<00:01:06.890> I'm<00:01:07.009> competing 00:01:07.330 --> 00:01:07.340 align:start position:0% this is the chip that I'm competing 00:01:07.340 --> 00:01:08.910 align:start position:0% this is the chip that I'm competing against 00:01:08.910 --> 00:01:08.920 align:start position:0% against 00:01:08.920 --> 00:01:13.480 align:start position:0% against there's<00:01:09.920> no<00:01:10.070> sound<00:01:10.479> it's<00:01:11.479> screaming<00:01:12.049> oh<00:01:12.590> well 00:01:13.480 --> 00:01:13.490 align:start position:0% there's no sound it's screaming oh well 00:01:13.490 --> 00:01:16.980 align:start position:0% there's no sound it's screaming oh well you<00:01:14.240> don't<00:01:14.420> get<00:01:14.630> to<00:01:14.689> enjoy<00:01:15.049> the<00:01:15.259> sound 00:01:16.980 --> 00:01:16.990 align:start position:0% you don't get to enjoy the sound 00:01:16.990 --> 00:01:19.870 align:start position:0% you don't get to enjoy the sound well<00:01:17.990> I<00:01:18.049> had<00:01:18.290> it<00:01:18.380> was<00:01:18.500> a<00:01:18.530> jet<00:01:18.950> this<00:01:19.640> is<00:01:19.700> a 00:01:19.870 --> 00:01:19.880 align:start position:0% well I had it was a jet this is a 00:01:19.880 --> 00:01:22.690 align:start position:0% well I had it was a jet this is a plymouth<00:01:20.390> belvedere<00:01:21.320> it's<00:01:22.159> a<00:01:22.280> comfortable 00:01:22.690 --> 00:01:22.700 align:start position:0% plymouth belvedere it's a comfortable 00:01:22.700 --> 00:01:24.810 align:start position:0% plymouth belvedere it's a comfortable family<00:01:23.030> sedan 00:01:24.810 --> 00:01:24.820 align:start position:0% family sedan 00:01:24.820 --> 00:01:27.960 align:start position:0% family sedan compared<00:01:25.820> the<00:01:25.940> digit<00:01:26.390> it<00:01:26.930> looked<00:01:27.140> like<00:01:27.350> this 00:01:27.960 --> 00:01:27.970 align:start position:0% compared the digit it looked like this 00:01:27.970 --> 00:01:31.120 align:start position:0% compared the digit it looked like this it<00:01:28.970> was<00:01:29.180> pathetic<00:01:29.810> it<00:01:30.229> was<00:01:30.409> really<00:01:30.950> pathetic 00:01:31.120 --> 00:01:31.130 align:start position:0% it was pathetic it was really pathetic 00:01:31.130 --> 00:01:35.160 align:start position:0% it was pathetic it was really pathetic and 00:01:35.160 --> 00:01:35.170 align:start position:0% 00:01:35.170 --> 00:01:37.920 align:start position:0% what<00:01:36.170> was<00:01:36.290> I<00:01:36.409> going<00:01:36.620> to<00:01:36.740> do 00:01:37.920 --> 00:01:37.930 align:start position:0% what was I going to do 00:01:37.930 --> 00:01:42.160 align:start position:0% what was I going to do okay<00:01:39.130> to<00:01:40.130> make<00:01:40.310> it<00:01:40.490> faster<00:01:41.180> the<00:01:41.300> first<00:01:41.570> thing<00:01:41.990> I 00:01:42.160 --> 00:01:42.170 align:start position:0% okay to make it faster the first thing I 00:01:42.170 --> 00:01:43.530 align:start position:0% okay to make it faster the first thing I wanted<00:01:42.560> to<00:01:42.740> do 00:01:43.530 --> 00:01:43.540 align:start position:0% wanted to do 00:01:43.540 --> 00:01:46.570 align:start position:0% wanted to do is<00:01:44.540> I<00:01:44.630> didn't<00:01:45.140> really<00:01:45.170> know<00:01:45.650> how<00:01:46.159> the<00:01:46.220> code 00:01:46.570 --> 00:01:46.580 align:start position:0% is I didn't really know how the code 00:01:46.580 --> 00:01:49.840 align:start position:0% is I didn't really know how the code worked<00:01:47.170> I<00:01:48.170> couldn't<00:01:48.830> really<00:01:48.979> understand<00:01:49.700> the 00:01:49.840 --> 00:01:49.850 align:start position:0% worked I couldn't really understand the 00:01:49.850 --> 00:01:52.180 align:start position:0% worked I couldn't really understand the yellow<00:01:50.120> paper<00:01:50.420> some<00:01:51.320> people<00:01:51.650> tell<00:01:51.860> me<00:01:51.890> it's 00:01:52.180 --> 00:01:52.190 align:start position:0% yellow paper some people tell me it's 00:01:52.190 --> 00:01:54.640 align:start position:0% yellow paper some people tell me it's wonderful<00:01:52.460> but<00:01:53.090> I'm<00:01:53.420> a<00:01:53.479> machinist<00:01:54.200> not<00:01:54.620> a 00:01:54.640 --> 00:01:54.650 align:start position:0% wonderful but I'm a machinist not a 00:01:54.650 --> 00:01:55.830 align:start position:0% wonderful but I'm a machinist not a mathematician 00:01:55.830 --> 00:01:55.840 align:start position:0% mathematician 00:01:55.840 --> 00:02:00.070 align:start position:0% mathematician so<00:01:56.840> the<00:01:56.990> idea<00:01:57.440> was<00:01:57.860> a<00:01:58.400> small<00:01:59.000> series<00:01:59.600> of 00:02:00.070 --> 00:02:00.080 align:start position:0% so the idea was a small series of 00:02:00.080 --> 00:02:02.910 align:start position:0% so the idea was a small series of correctness<00:02:01.040> preserving<00:02:01.850> transformations 00:02:02.910 --> 00:02:02.920 align:start position:0% correctness preserving transformations 00:02:02.920 --> 00:02:05.440 align:start position:0% correctness preserving transformations assuming<00:02:03.920> the<00:02:04.040> code<00:02:04.250> was<00:02:04.520> correct<00:02:04.940> to<00:02:05.090> begin 00:02:05.440 --> 00:02:05.450 align:start position:0% assuming the code was correct to begin 00:02:05.450 --> 00:02:08.770 align:start position:0% assuming the code was correct to begin with<00:02:05.750> I<00:02:06.080> make<00:02:06.530> a<00:02:06.560> small<00:02:06.830> change<00:02:07.010> and<00:02:07.940> I<00:02:08.479> run<00:02:08.750> a 00:02:08.770 --> 00:02:08.780 align:start position:0% with I make a small change and I run a 00:02:08.780 --> 00:02:12.520 align:start position:0% with I make a small change and I run a test<00:02:09.170> and<00:02:09.640> Dmitry<00:02:10.640> here<00:02:11.120> had<00:02:11.659> a<00:02:11.689> wonderful 00:02:12.520 --> 00:02:12.530 align:start position:0% test and Dmitry here had a wonderful 00:02:12.530 --> 00:02:16.030 align:start position:0% test and Dmitry here had a wonderful suite<00:02:12.860> of<00:02:13.040> tests<00:02:13.580> I'm<00:02:14.090> not<00:02:14.360> sure<00:02:14.750> how<00:02:15.530> many<00:02:15.739> how 00:02:16.030 --> 00:02:16.040 align:start position:0% suite of tests I'm not sure how many how 00:02:16.040 --> 00:02:19.119 align:start position:0% suite of tests I'm not sure how many how many<00:02:16.069> tests<00:02:16.640> are<00:02:16.819> there<00:02:17.030> Dmitry<00:02:17.720> I<00:02:17.930> know<00:02:18.860> at 00:02:19.119 --> 00:02:19.129 align:start position:0% many tests are there Dmitry I know at 00:02:19.129 --> 00:02:22.660 align:start position:0% many tests are there Dmitry I know at one<00:02:19.159> point<00:02:19.340> I<00:02:19.790> broke<00:02:20.060> thousands<00:02:20.870> of<00:02:21.049> them<00:02:21.670> and 00:02:22.660 --> 00:02:22.670 align:start position:0% one point I broke thousands of them and 00:02:22.670 --> 00:02:25.750 align:start position:0% one point I broke thousands of them and I<00:02:23.540> wasn't<00:02:23.780> looking<00:02:24.110> to<00:02:24.349> make<00:02:24.620> any<00:02:24.860> structural 00:02:25.750 --> 00:02:25.760 align:start position:0% I wasn't looking to make any structural 00:02:25.760 --> 00:02:28.670 align:start position:0% I wasn't looking to make any structural changes<00:02:26.480> to<00:02:26.540> the<00:02:26.810> machine 00:02:28.670 --> 00:02:28.680 align:start position:0% changes to the machine 00:02:28.680 --> 00:02:32.640 align:start position:0% changes to the machine just<00:02:29.680> make<00:02:30.220> just<00:02:31.209> get<00:02:31.510> out<00:02:31.750> of<00:02:31.780> the<00:02:32.140> way 00:02:32.640 --> 00:02:32.650 align:start position:0% just make just get out of the way 00:02:32.650 --> 00:02:34.470 align:start position:0% just make just get out of the way anything<00:02:33.310> that<00:02:33.549> was<00:02:33.670> hurting<00:02:34.090> the 00:02:34.470 --> 00:02:34.480 align:start position:0% anything that was hurting the 00:02:34.480 --> 00:02:37.830 align:start position:0% anything that was hurting the performance<00:02:35.310> a<00:02:36.310> lot<00:02:36.790> of<00:02:36.939> it<00:02:37.090> a<00:02:37.269> lot<00:02:37.390> of<00:02:37.629> the 00:02:37.830 --> 00:02:37.840 align:start position:0% performance a lot of it a lot of the 00:02:37.840 --> 00:02:39.809 align:start position:0% performance a lot of it a lot of the instructions<00:02:38.620> were<00:02:38.890> using<00:02:39.340> infinite 00:02:39.809 --> 00:02:39.819 align:start position:0% instructions were using infinite 00:02:39.819 --> 00:02:42.740 align:start position:0% instructions were using infinite precision<00:02:39.970> arithmetic 00:02:42.740 --> 00:02:42.750 align:start position:0% precision arithmetic 00:02:42.750 --> 00:02:45.720 align:start position:0% precision arithmetic almost<00:02:43.750> none<00:02:44.019> of<00:02:44.049> them<00:02:44.290> needed<00:02:44.769> to<00:02:45.010> I<00:02:45.280> was<00:02:45.549> able 00:02:45.720 --> 00:02:45.730 align:start position:0% almost none of them needed to I was able 00:02:45.730 --> 00:02:49.670 align:start position:0% almost none of them needed to I was able to<00:02:46.000> get<00:02:46.150> away<00:02:46.329> with<00:02:46.659> 512<00:02:47.650> bits<00:02:48.329> the<00:02:49.329> gas 00:02:49.670 --> 00:02:49.680 align:start position:0% to get away with 512 bits the gas 00:02:49.680 --> 00:02:52.830 align:start position:0% to get away with 512 bits the gas calculations<00:02:50.680> were<00:02:50.950> being<00:02:51.190> done<00:02:51.370> with<00:02:51.840> 256 00:02:52.830 --> 00:02:52.840 align:start position:0% calculations were being done with 256 00:02:52.840 --> 00:02:53.869 align:start position:0% calculations were being done with 256 bits 00:02:53.869 --> 00:02:53.879 align:start position:0% bits 00:02:53.879 --> 00:02:57.089 align:start position:0% bits the<00:02:54.879> Go<00:02:55.060> machine<00:02:55.299> had<00:02:55.840> already<00:02:56.019> switched<00:02:56.829> to 00:02:57.089 --> 00:02:57.099 align:start position:0% the Go machine had already switched to 00:02:57.099 --> 00:02:59.479 align:start position:0% the Go machine had already switched to 64<00:02:57.849> bits 00:02:59.479 --> 00:02:59.489 align:start position:0% 64 bits 00:02:59.489 --> 00:03:01.369 align:start position:0% 64 bits to<00:03:00.489> the<00:03:00.670> de 00:03:01.369 --> 00:03:01.379 align:start position:0% to the de 00:03:01.379 --> 00:03:03.830 align:start position:0% to the de 256<00:03:02.379> is 00:03:03.830 --> 00:03:03.840 align:start position:0% 256 is 00:03:03.840 --> 00:03:06.330 align:start position:0% 256 is approximately<00:03:04.840> the<00:03:05.049> number<00:03:05.079> of<00:03:05.560> atoms<00:03:06.040> in<00:03:06.280> the 00:03:06.330 --> 00:03:06.340 align:start position:0% approximately the number of atoms in the 00:03:06.340 --> 00:03:09.119 align:start position:0% approximately the number of atoms in the universe<00:03:06.930> which<00:03:07.930> I<00:03:08.230> thought<00:03:08.440> was<00:03:08.709> probably 00:03:09.119 --> 00:03:09.129 align:start position:0% universe which I thought was probably 00:03:09.129 --> 00:03:12.599 align:start position:0% universe which I thought was probably more<00:03:09.790> gas<00:03:10.060> than<00:03:10.090> anybody<00:03:10.720> was<00:03:11.709> ever<00:03:11.920> going<00:03:12.280> to 00:03:12.599 --> 00:03:12.609 align:start position:0% more gas than anybody was ever going to 00:03:12.609 --> 00:03:14.309 align:start position:0% more gas than anybody was ever going to need 00:03:14.309 --> 00:03:14.319 align:start position:0% need 00:03:14.319 --> 00:03:19.259 align:start position:0% need so<00:03:14.889> in<00:03:15.099> general<00:03:15.840> also<00:03:16.840> there<00:03:17.709> was<00:03:17.980> one<00:03:18.459> routine 00:03:19.259 --> 00:03:19.269 align:start position:0% so in general also there was one routine 00:03:19.269 --> 00:03:21.390 align:start position:0% so in general also there was one routine which<00:03:19.659> was<00:03:19.840> doing<00:03:20.049> all<00:03:20.470> of<00:03:20.500> the<00:03:20.859> gas<00:03:21.069> and 00:03:21.390 --> 00:03:21.400 align:start position:0% which was doing all of the gas and 00:03:21.400 --> 00:03:24.750 align:start position:0% which was doing all of the gas and memory<00:03:22.200> computations<00:03:23.200> it<00:03:23.769> was<00:03:23.980> doing<00:03:24.400> it<00:03:24.519> for 00:03:24.750 --> 00:03:24.760 align:start position:0% memory computations it was doing it for 00:03:24.760 --> 00:03:27.420 align:start position:0% memory computations it was doing it for every<00:03:25.209> single<00:03:25.440> instruction<00:03:26.440> that<00:03:26.590> it<00:03:26.739> ran<00:03:27.010> and 00:03:27.420 --> 00:03:27.430 align:start position:0% every single instruction that it ran and 00:03:27.430 --> 00:03:30.059 align:start position:0% every single instruction that it ran and that<00:03:28.239> routine<00:03:28.780> was<00:03:28.810> generally<00:03:29.799> more 00:03:30.059 --> 00:03:30.069 align:start position:0% that routine was generally more 00:03:30.069 --> 00:03:33.990 align:start position:0% that routine was generally more expensive<00:03:30.609> than<00:03:31.569> the<00:03:31.659> computation<00:03:32.530> itself<00:03:33.040> so 00:03:33.990 --> 00:03:34.000 align:start position:0% expensive than the computation itself so 00:03:34.000 --> 00:03:36.000 align:start position:0% expensive than the computation itself so that<00:03:34.239> was<00:03:34.480> a<00:03:34.510> matter<00:03:34.840> of<00:03:35.019> breaking<00:03:35.379> it<00:03:35.739> into 00:03:36.000 --> 00:03:36.010 align:start position:0% that was a matter of breaking it into 00:03:36.010 --> 00:03:38.610 align:start position:0% that was a matter of breaking it into little<00:03:36.190> pieces<00:03:36.310> and<00:03:37.120> running<00:03:37.870> only<00:03:38.049> those 00:03:38.610 --> 00:03:38.620 align:start position:0% little pieces and running only those 00:03:38.620 --> 00:03:41.729 align:start position:0% little pieces and running only those pieces<00:03:39.010> that<00:03:39.280> were<00:03:39.609> relevant<00:03:40.030> to<00:03:40.510> the<00:03:41.290> routine 00:03:41.729 --> 00:03:41.739 align:start position:0% pieces that were relevant to the routine 00:03:41.739 --> 00:03:44.629 align:start position:0% pieces that were relevant to the routine that<00:03:42.400> I<00:03:42.549> was<00:03:42.699> trying<00:03:42.940> to<00:03:43.209> run 00:03:44.629 --> 00:03:44.639 align:start position:0% that I was trying to run 00:03:44.639 --> 00:03:46.550 align:start position:0% that I was trying to run doo<00:03:45.639> doo 00:03:46.550 --> 00:03:46.560 align:start position:0% doo doo 00:03:46.560 --> 00:03:49.729 align:start position:0% doo doo there<00:03:47.560> it<00:03:47.769> goes<00:03:48.010> and<00:03:48.340> so<00:03:49.060> when<00:03:49.269> you're<00:03:49.419> done 00:03:49.729 --> 00:03:49.739 align:start position:0% there it goes and so when you're done 00:03:49.739 --> 00:03:52.500 align:start position:0% there it goes and so when you're done you've<00:03:50.739> stripped<00:03:51.099> out<00:03:51.400> everything<00:03:52.150> from<00:03:52.389> that 00:03:52.500 --> 00:03:52.510 align:start position:0% you've stripped out everything from that 00:03:52.510 --> 00:03:54.689 align:start position:0% you've stripped out everything from that Belvedere<00:03:53.260> that<00:03:53.530> was<00:03:53.650> in<00:03:53.829> the<00:03:53.949> way<00:03:54.099> of<00:03:54.280> making 00:03:54.689 --> 00:03:54.699 align:start position:0% Belvedere that was in the way of making 00:03:54.699 --> 00:03:57.839 align:start position:0% Belvedere that was in the way of making it<00:03:54.730> go<00:03:54.940> faster<00:03:55.599> and<00:03:55.870> you<00:03:56.739> have<00:03:56.980> the<00:03:57.310> roadrunner 00:03:57.839 --> 00:03:57.849 align:start position:0% it go faster and you have the roadrunner 00:03:57.849 --> 00:04:00.809 align:start position:0% it go faster and you have the roadrunner which<00:03:58.510> was<00:03:58.780> Plymouth's<00:03:59.620> attempt<00:03:59.980> to<00:04:00.250> compete 00:04:00.809 --> 00:04:00.819 align:start position:0% which was Plymouth's attempt to compete 00:04:00.819 --> 00:04:05.270 align:start position:0% which was Plymouth's attempt to compete with<00:04:01.060> the<00:04:01.209> Dodge<00:04:01.440> Charger<00:04:02.440> and 00:04:05.270 --> 00:04:05.280 align:start position:0% 00:04:05.280 --> 00:04:09.119 align:start position:0% it<00:04:06.280> did<00:04:06.549> pretty<00:04:06.790> well<00:04:06.940> yeah<00:04:07.870> and<00:04:08.349> this<00:04:08.739> is<00:04:08.799> the 00:04:09.119 --> 00:04:09.129 align:start position:0% it did pretty well yeah and this is the 00:04:09.129 --> 00:04:11.369 align:start position:0% it did pretty well yeah and this is the interpreter<00:04:09.790> which<00:04:10.239> is<00:04:10.419> shipping<00:04:10.810> in<00:04:10.959> today's 00:04:11.369 --> 00:04:11.379 align:start position:0% interpreter which is shipping in today's 00:04:11.379 --> 00:04:12.649 align:start position:0% interpreter which is shipping in today's code 00:04:12.649 --> 00:04:12.659 align:start position:0% code 00:04:12.659 --> 00:04:15.659 align:start position:0% code the<00:04:13.659> loop<00:04:13.900> test<00:04:14.290> it's<00:04:14.799> hard<00:04:15.040> to<00:04:15.220> make<00:04:15.400> much 00:04:15.659 --> 00:04:15.669 align:start position:0% the loop test it's hard to make much 00:04:15.669 --> 00:04:18.779 align:start position:0% the loop test it's hard to make much faster<00:04:16.299> it<00:04:16.570> just<00:04:16.840> goes<00:04:17.049> in<00:04:17.289> a<00:04:17.380> circle<00:04:17.859> and<00:04:18.070> the 00:04:18.779 --> 00:04:18.789 align:start position:0% faster it just goes in a circle and the 00:04:18.789 --> 00:04:21.180 align:start position:0% faster it just goes in a circle and the jet<00:04:19.030> sees<00:04:19.299> that<00:04:19.599> circle<00:04:20.139> and<00:04:20.260> reduces<00:04:20.859> it<00:04:21.039> to 00:04:21.180 --> 00:04:21.190 align:start position:0% jet sees that circle and reduces it to 00:04:21.190 --> 00:04:24.810 align:start position:0% jet sees that circle and reduces it to almost<00:04:21.310> nothing<00:04:22.300> the<00:04:23.110> R&G<00:04:23.620> test<00:04:24.220> is<00:04:24.669> a<00:04:24.699> little 00:04:24.810 --> 00:04:24.820 align:start position:0% almost nothing the R&G test is a little 00:04:24.820 --> 00:04:27.870 align:start position:0% almost nothing the R&G test is a little random<00:04:25.270> number<00:04:25.900> generator<00:04:26.530> old-style<00:04:27.370> news 00:04:27.870 --> 00:04:27.880 align:start position:0% random number generator old-style news 00:04:27.880 --> 00:04:30.860 align:start position:0% random number generator old-style news generator<00:04:28.599> just<00:04:29.409> as<00:04:29.560> a<00:04:29.590> lot<00:04:29.860> of<00:04:29.889> computation 00:04:30.860 --> 00:04:30.870 align:start position:0% generator just as a lot of computation 00:04:30.870 --> 00:04:34.080 align:start position:0% generator just as a lot of computation that's<00:04:31.870> respectably<00:04:32.770> faster<00:04:33.490> not<00:04:33.820> where<00:04:34.060> I 00:04:34.080 --> 00:04:34.090 align:start position:0% that's respectably faster not where I 00:04:34.090 --> 00:04:37.920 align:start position:0% that's respectably faster not where I wanted<00:04:34.539> it<00:04:34.720> the<00:04:35.380> RC<00:04:35.740> 5<00:04:36.070> interpreter<00:04:36.969> is<00:04:37.300> the 00:04:37.920 --> 00:04:37.930 align:start position:0% wanted it the RC 5 interpreter is the 00:04:37.930 --> 00:04:41.540 align:start position:0% wanted it the RC 5 interpreter is the old<00:04:38.050> RC<00:04:38.560> 5<00:04:38.800> cipher<00:04:39.520> so<00:04:40.380> it's<00:04:40.770> not<00:04:40.980> much<00:04:41.220> used 00:04:41.540 --> 00:04:41.550 align:start position:0% old RC 5 cipher so it's not much used 00:04:41.550 --> 00:04:43.820 align:start position:0% old RC 5 cipher so it's not much used anymore<00:04:42.180> but<00:04:42.450> it's<00:04:42.600> a<00:04:42.720> good<00:04:42.930> example<00:04:43.080> of<00:04:43.680> an 00:04:43.820 --> 00:04:43.830 align:start position:0% anymore but it's a good example of an 00:04:43.830 --> 00:04:46.330 align:start position:0% anymore but it's a good example of an actual<00:04:44.370> program 00:04:46.330 --> 00:04:46.340 align:start position:0% actual program 00:04:46.340 --> 00:04:49.870 align:start position:0% actual program and<00:04:47.360> to<00:04:48.360> get<00:04:48.600> from<00:04:48.900> there 00:04:49.870 --> 00:04:49.880 align:start position:0% and to get from there 00:04:49.880 --> 00:04:54.050 align:start position:0% and to get from there the<00:04:50.880> approach<00:04:51.380> was<00:04:52.380> to<00:04:52.980> start<00:04:53.280> making<00:04:53.580> more 00:04:54.050 --> 00:04:54.060 align:start position:0% the approach was to start making more 00:04:54.060 --> 00:04:57.260 align:start position:0% the approach was to start making more actual<00:04:54.780> changes<00:04:55.620> to<00:04:55.830> the<00:04:55.950> structure<00:04:56.370> of<00:04:57.000> the 00:04:57.260 --> 00:04:57.270 align:start position:0% actual changes to the structure of the 00:04:57.270 --> 00:05:01.430 align:start position:0% actual changes to the structure of the interpreter<00:04:58.050> so<00:04:58.770> I<00:04:58.800> wanted<00:04:59.430> some<00:05:00.240> new<00:05:00.440> faster 00:05:01.430 --> 00:05:01.440 align:start position:0% interpreter so I wanted some new faster 00:05:01.440 --> 00:05:05.960 align:start position:0% interpreter so I wanted some new faster op<00:05:01.620> codes<00:05:02.040> I<00:05:02.840> wanted<00:05:03.840> a<00:05:04.080> constant<00:05:04.830> pool<00:05:05.040> that 00:05:05.960 --> 00:05:05.970 align:start position:0% op codes I wanted a constant pool that 00:05:05.970 --> 00:05:06.700 align:start position:0% op codes I wanted a constant pool that is 00:05:06.700 --> 00:05:06.710 align:start position:0% is 00:05:06.710 --> 00:05:09.740 align:start position:0% is currently<00:05:07.710> if<00:05:08.130> there's<00:05:08.430> a<00:05:08.490> push<00:05:08.790> instruction 00:05:09.740 --> 00:05:09.750 align:start position:0% currently if there's a push instruction 00:05:09.750 --> 00:05:13.010 align:start position:0% currently if there's a push instruction the<00:05:10.290> constant<00:05:10.950> to<00:05:11.100> be<00:05:11.250> pushed<00:05:11.640> is<00:05:12.240> laid<00:05:12.750> out 00:05:13.010 --> 00:05:13.020 align:start position:0% the constant to be pushed is laid out 00:05:13.020 --> 00:05:15.980 align:start position:0% the constant to be pushed is laid out right<00:05:13.800> in<00:05:14.040> the<00:05:14.190> byte<00:05:14.430> code<00:05:14.480> it's<00:05:15.480> a<00:05:15.720> most 00:05:15.980 --> 00:05:15.990 align:start position:0% right in the byte code it's a most 00:05:15.990 --> 00:05:18.890 align:start position:0% right in the byte code it's a most significant<00:05:16.680> byte<00:05:16.920> first<00:05:17.370> order<00:05:18.000> and<00:05:18.300> it<00:05:18.690> has 00:05:18.890 --> 00:05:18.900 align:start position:0% significant byte first order and it has 00:05:18.900 --> 00:05:21.340 align:start position:0% significant byte first order and it has to<00:05:19.140> be<00:05:19.260> loaded<00:05:19.530> up<00:05:19.890> into 00:05:21.340 --> 00:05:21.350 align:start position:0% to be loaded up into 00:05:21.350 --> 00:05:25.520 align:start position:0% to be loaded up into the<00:05:22.350> stack<00:05:22.650> one<00:05:23.370> byte<00:05:23.700> at<00:05:23.730> a<00:05:24.000> time<00:05:24.030> so<00:05:24.900> I<00:05:24.930> create 00:05:25.520 --> 00:05:25.530 align:start position:0% the stack one byte at a time so I create 00:05:25.530 --> 00:05:26.440 align:start position:0% the stack one byte at a time so I create a<00:05:25.560> pool<00:05:25.890> of 00:05:26.440 --> 00:05:26.450 align:start position:0% a pool of 00:05:26.450 --> 00:05:29.840 align:start position:0% a pool of pre-loaded<00:05:27.450> constants<00:05:28.140> I<00:05:28.500> can<00:05:29.040> index<00:05:29.520> them 00:05:29.840 --> 00:05:29.850 align:start position:0% pre-loaded constants I can index them 00:05:29.850 --> 00:05:33.230 align:start position:0% pre-loaded constants I can index them with<00:05:30.120> one<00:05:30.390> byte<00:05:30.720> and<00:05:31.490> move<00:05:32.490> the<00:05:32.730> Bandhu<00:05:33.090> to 00:05:33.230 --> 00:05:33.240 align:start position:0% with one byte and move the Bandhu to 00:05:33.240 --> 00:05:36.220 align:start position:0% with one byte and move the Bandhu to stack<00:05:33.510> with<00:05:33.810> a<00:05:33.840> quick<00:05:34.110> assignment 00:05:36.220 --> 00:05:36.230 align:start position:0% stack with a quick assignment 00:05:36.230 --> 00:05:39.980 align:start position:0% stack with a quick assignment so<00:05:37.230> that's<00:05:37.710> specifically<00:05:38.490> a<00:05:39.000> new<00:05:39.060> push<00:05:39.600> see 00:05:39.980 --> 00:05:39.990 align:start position:0% so that's specifically a new push see 00:05:39.990 --> 00:05:42.920 align:start position:0% so that's specifically a new push see instruction<00:05:40.950> that<00:05:41.610> just<00:05:41.850> has<00:05:42.060> that<00:05:42.270> one<00:05:42.540> byte 00:05:42.920 --> 00:05:42.930 align:start position:0% instruction that just has that one byte 00:05:42.930 --> 00:05:47.300 align:start position:0% instruction that just has that one byte yeah<00:05:43.740> so<00:05:44.670> I<00:05:44.730> can<00:05:44.940> just<00:05:45.180> index<00:05:45.690> in<00:05:46.070> the<00:05:47.070> other 00:05:47.300 --> 00:05:47.310 align:start position:0% yeah so I can just index in the other 00:05:47.310 --> 00:05:50.000 align:start position:0% yeah so I can just index in the other thing<00:05:47.670> I<00:05:47.880> did<00:05:47.940> which<00:05:48.630> Jeffrey<00:05:49.200> is<00:05:49.320> also<00:05:49.770> done 00:05:50.000 --> 00:05:50.010 align:start position:0% thing I did which Jeffrey is also done 00:05:50.010 --> 00:05:54.110 align:start position:0% thing I did which Jeffrey is also done in<00:05:50.220> the<00:05:50.250> go<00:05:50.490> interpreter<00:05:51.300> is<00:05:51.860> that<00:05:52.860> all<00:05:53.670> of<00:05:53.970> the 00:05:54.110 --> 00:05:54.120 align:start position:0% in the go interpreter is that all of the 00:05:54.120 --> 00:05:57.860 align:start position:0% in the go interpreter is that all of the jumps<00:05:54.690> in<00:05:55.020> the<00:05:55.380> evm<00:05:55.860> are<00:05:56.550> computed<00:05:57.270> go<00:05:57.510> choose 00:05:57.860 --> 00:05:57.870 align:start position:0% jumps in the evm are computed go choose 00:05:57.870 --> 00:06:00.740 align:start position:0% jumps in the evm are computed go choose how<00:05:58.650> many<00:05:58.710> Fortran<00:05:59.520> programmers<00:06:00.270> left<00:06:00.570> in 00:06:00.740 --> 00:06:00.750 align:start position:0% how many Fortran programmers left in 00:06:00.750 --> 00:06:01.810 align:start position:0% how many Fortran programmers left in this<00:06:00.930> room 00:06:01.810 --> 00:06:01.820 align:start position:0% this room 00:06:01.820 --> 00:06:07.540 align:start position:0% this room Wow<00:06:03.240> three<00:06:03.750> I<00:06:04.340> make<00:06:05.340> four<00:06:05.700> that's<00:06:06.300> scary 00:06:07.540 --> 00:06:07.550 align:start position:0% Wow three I make four that's scary 00:06:07.550 --> 00:06:10.340 align:start position:0% Wow three I make four that's scary it's<00:06:08.550> the<00:06:08.640> only<00:06:08.760> language<00:06:09.060> I<00:06:09.420> recall<00:06:09.840> besides 00:06:10.340 --> 00:06:10.350 align:start position:0% it's the only language I recall besides 00:06:10.350 --> 00:06:13.210 align:start position:0% it's the only language I recall besides assembly<00:06:11.040> with<00:06:11.220> computed<00:06:11.820> go<00:06:12.030> choose 00:06:13.210 --> 00:06:13.220 align:start position:0% assembly with computed go choose 00:06:13.220 --> 00:06:16.040 align:start position:0% assembly with computed go choose trouble<00:06:14.220> with<00:06:14.400> the<00:06:14.520> computed<00:06:15.090> goto<00:06:15.300> is<00:06:15.840> at 00:06:16.040 --> 00:06:16.050 align:start position:0% trouble with the computed goto is at 00:06:16.050 --> 00:06:18.920 align:start position:0% trouble with the computed goto is at runtime<00:06:16.320> you<00:06:17.010> have<00:06:17.580> to<00:06:17.760> check<00:06:18.120> as<00:06:18.420> to<00:06:18.480> whether 00:06:18.920 --> 00:06:18.930 align:start position:0% runtime you have to check as to whether 00:06:18.930 --> 00:06:21.920 align:start position:0% runtime you have to check as to whether the<00:06:19.200> go-to<00:06:19.440> is<00:06:19.890> going<00:06:20.280> to<00:06:20.520> somewhere<00:06:20.970> valid<00:06:21.570> or 00:06:21.920 --> 00:06:21.930 align:start position:0% the go-to is going to somewhere valid or 00:06:21.930 --> 00:06:24.220 align:start position:0% the go-to is going to somewhere valid or just<00:06:22.380> landing<00:06:22.890> in<00:06:23.010> the<00:06:23.130> middle<00:06:23.460> of<00:06:23.580> nowhere 00:06:24.220 --> 00:06:24.230 align:start position:0% just landing in the middle of nowhere 00:06:24.230 --> 00:06:26.660 align:start position:0% just landing in the middle of nowhere and<00:06:25.230> that<00:06:25.530> takes<00:06:25.860> time 00:06:26.660 --> 00:06:26.670 align:start position:0% and that takes time 00:06:26.670 --> 00:06:31.040 align:start position:0% and that takes time so<00:06:27.360> what<00:06:27.660> we<00:06:27.840> do<00:06:28.080> is<00:06:28.500> at<00:06:29.070> load<00:06:29.400> time<00:06:29.570> we<00:06:30.570> look<00:06:30.840> to 00:06:31.040 --> 00:06:31.050 align:start position:0% so what we do is at load time we look to 00:06:31.050 --> 00:06:34.670 align:start position:0% so what we do is at load time we look to see<00:06:31.380> is<00:06:32.070> the<00:06:32.460> place<00:06:32.700> is<00:06:32.970> going<00:06:33.330> to<00:06:33.510> constant<00:06:34.260> is 00:06:34.670 --> 00:06:34.680 align:start position:0% see is the place is going to constant is 00:06:34.680 --> 00:06:37.730 align:start position:0% see is the place is going to constant is the<00:06:34.980> place<00:06:35.250> that's<00:06:35.520> going<00:06:35.880> to<00:06:36.030> correct<00:06:36.630> if<00:06:37.170> so 00:06:37.730 --> 00:06:37.740 align:start position:0% the place that's going to correct if so 00:06:37.740 --> 00:06:41.300 align:start position:0% the place that's going to correct if so I<00:06:38.130> replaced<00:06:38.910> the<00:06:39.180> jump<00:06:39.540> with<00:06:39.930> a<00:06:39.960> jump<00:06:40.350> V<00:06:40.650> or<00:06:41.280> a 00:06:41.300 --> 00:06:41.310 align:start position:0% I replaced the jump with a jump V or a 00:06:41.310 --> 00:06:44.630 align:start position:0% I replaced the jump with a jump V or a jump<00:06:41.610> V<00:06:41.850> I<00:06:41.880> and<00:06:42.480> I<00:06:42.900> can<00:06:42.930> just<00:06:43.320> do<00:06:43.560> the<00:06:43.800> jump<00:06:44.130> at 00:06:44.630 --> 00:06:44.640 align:start position:0% jump V I and I can just do the jump at 00:06:44.640 --> 00:06:47.690 align:start position:0% jump V I and I can just do the jump at runtime<00:06:45.000> and<00:06:45.600> the<00:06:46.020> both<00:06:46.230> the<00:06:46.470> go<00:06:46.650> and<00:06:46.890> the<00:06:46.980> C++ 00:06:47.690 --> 00:06:47.700 align:start position:0% runtime and the both the go and the C++ 00:06:47.700 --> 00:06:49.730 align:start position:0% runtime and the both the go and the C++ interpreters<00:06:48.510> have<00:06:49.020> found<00:06:49.290> that<00:06:49.500> to<00:06:49.560> be 00:06:49.730 --> 00:06:49.740 align:start position:0% interpreters have found that to be 00:06:49.740 --> 00:06:52.580 align:start position:0% interpreters have found that to be pretty<00:06:49.890> advantageous 00:06:52.580 --> 00:06:52.590 align:start position:0% pretty advantageous 00:06:52.590 --> 00:06:57.050 align:start position:0% pretty advantageous and<00:06:53.180> so<00:06:54.180> tomorrow's<00:06:55.110> interpreter<00:06:55.919> which<00:06:56.759> is 00:06:57.050 --> 00:06:57.060 align:start position:0% and so tomorrow's interpreter which is 00:06:57.060 --> 00:06:59.900 align:start position:0% and so tomorrow's interpreter which is running<00:06:57.300> on<00:06:57.569> my<00:06:58.050> machine<00:06:58.259> right<00:06:58.800> now<00:06:58.830> and<00:06:59.729> not 00:06:59.900 --> 00:06:59.910 align:start position:0% running on my machine right now and not 00:06:59.910 --> 00:07:01.809 align:start position:0% running on my machine right now and not anywhere<00:07:00.330> else 00:07:01.809 --> 00:07:01.819 align:start position:0% anywhere else 00:07:01.819 --> 00:07:05.120 align:start position:0% anywhere else we're<00:07:02.819> strong<00:07:03.060> you<00:07:03.240> look<00:07:03.449> pretty<00:07:03.690> good<00:07:04.130> the 00:07:05.120 --> 00:07:05.130 align:start position:0% we're strong you look pretty good the 00:07:05.130 --> 00:07:06.770 align:start position:0% we're strong you look pretty good the loops<00:07:05.340> a<00:07:05.550> little<00:07:05.819> better<00:07:06.030> still<00:07:06.599> not 00:07:06.770 --> 00:07:06.780 align:start position:0% loops a little better still not 00:07:06.780 --> 00:07:09.710 align:start position:0% loops a little better still not wonderful<00:07:07.470> the<00:07:08.069> random<00:07:08.460> number<00:07:08.759> generator<00:07:08.789> is 00:07:09.710 --> 00:07:09.720 align:start position:0% wonderful the random number generator is 00:07:09.720 --> 00:07:11.659 align:start position:0% wonderful the random number generator is starting<00:07:10.110> to<00:07:10.229> get<00:07:10.410> pretty<00:07:10.710> competitive<00:07:10.919> with 00:07:11.659 --> 00:07:11.669 align:start position:0% starting to get pretty competitive with 00:07:11.669 --> 00:07:13.059 align:start position:0% starting to get pretty competitive with the<00:07:11.789> chip<00:07:12.060> and 00:07:13.059 --> 00:07:13.069 align:start position:0% the chip and 00:07:13.069 --> 00:07:16.749 align:start position:0% the chip and our<00:07:14.069> c5<00:07:14.550> is<00:07:14.819> really<00:07:15.449> doing<00:07:15.750> pretty<00:07:16.020> well 00:07:16.749 --> 00:07:16.759 align:start position:0% our c5 is really doing pretty well 00:07:16.759 --> 00:07:19.520 align:start position:0% our c5 is really doing pretty well Paul's<00:07:17.759> got<00:07:18.090> some<00:07:18.330> work<00:07:18.539> to<00:07:18.750> do<00:07:18.870> to<00:07:19.050> catch<00:07:19.259> up 00:07:19.520 --> 00:07:19.530 align:start position:0% Paul's got some work to do to catch up 00:07:19.530 --> 00:07:20.620 align:start position:0% Paul's got some work to do to catch up with<00:07:19.740> me 00:07:20.620 --> 00:07:20.630 align:start position:0% with me 00:07:20.630 --> 00:07:22.420 align:start position:0% with me and 00:07:22.420 --> 00:07:22.430 align:start position:0% and 00:07:22.430 --> 00:07:26.779 align:start position:0% and here<00:07:23.430> we<00:07:23.580> have<00:07:23.759> a<00:07:23.789> race<00:07:24.180> we<00:07:24.870> have<00:07:25.169> the<00:07:25.680> JIT<00:07:26.490> is 00:07:26.779 --> 00:07:26.789 align:start position:0% here we have a race we have the JIT is 00:07:26.789 --> 00:07:31.779 align:start position:0% here we have a race we have the JIT is the<00:07:26.940> charger<00:07:27.539> on<00:07:27.930> the<00:07:28.830> left<00:07:29.070> and<00:07:29.660> we<00:07:30.660> have<00:07:30.690> the 00:07:31.779 --> 00:07:31.789 align:start position:0% the charger on the left and we have the 00:07:31.789 --> 00:07:35.210 align:start position:0% the charger on the left and we have the interpreter<00:07:32.789> on<00:07:33.030> the<00:07:33.270> right<00:07:33.509> and<00:07:34.050> make<00:07:34.979> it 00:07:35.210 --> 00:07:35.220 align:start position:0% interpreter on the right and make it 00:07:35.220 --> 00:07:36.159 align:start position:0% interpreter on the right and make it scream 00:07:36.159 --> 00:07:36.169 align:start position:0% scream 00:07:36.169 --> 00:07:38.770 align:start position:0% scream roll<00:07:37.169> it 00:07:38.770 --> 00:07:38.780 align:start position:0% roll it 00:07:38.780 --> 00:07:44.980 align:start position:0% roll it burn<00:07:39.780> soup<00:07:40.110> go 00:07:44.980 --> 00:07:44.990 align:start position:0% 00:07:44.990 --> 00:07:48.439 align:start position:0% there<00:07:45.990> it's<00:07:46.110> a<00:07:46.169> video<00:07:46.470> to<00:07:46.590> play<00:07:46.919> here<00:07:47.449> somebody 00:07:48.439 --> 00:07:48.449 align:start position:0% there it's a video to play here somebody 00:07:48.449 --> 00:07:55.270 align:start position:0% there it's a video to play here somebody knows<00:07:48.659> how<00:07:48.840> to<00:07:48.900> play<00:07:49.199> it 00:07:55.270 --> 00:07:55.280 align:start position:0% 00:07:55.280 --> 00:07:57.790 align:start position:0% no<00:07:56.280> no 00:07:57.790 --> 00:07:57.800 align:start position:0% no no 00:07:57.800 --> 00:08:03.410 align:start position:0% no no this<00:07:58.800> guy<00:07:59.039> he's<00:07:59.880> a<00:07:59.909> video<00:08:00.389> he<00:08:00.690> plays 00:08:03.410 --> 00:08:03.420 align:start position:0% 00:08:03.420 --> 00:08:10.530 align:start position:0% [Music] 00:08:10.530 --> 00:08:10.540 align:start position:0% [Music] 00:08:10.540 --> 00:08:12.230 align:start position:0% [Music] it's<00:08:10.990> where<00:08:11.320> a 00:08:12.230 --> 00:08:12.240 align:start position:0% it's where a 00:08:12.240 --> 00:08:17.180 align:start position:0% it's where a magic 00:08:17.180 --> 00:08:17.190 align:start position:0% 00:08:17.190 --> 00:08:21.230 align:start position:0% that's<00:08:18.190> a<00:08:18.370> quarter-mile 00:08:21.230 --> 00:08:21.240 align:start position:0% 00:08:21.240 --> 00:08:23.850 align:start position:0% deck<00:08:22.240> Vitesse<00:08:22.660> list<00:08:22.990> they<00:08:23.169> don't<00:08:23.350> burn<00:08:23.500> enough 00:08:23.850 --> 00:08:23.860 align:start position:0% deck Vitesse list they don't burn enough 00:08:23.860 --> 00:08:29.210 align:start position:0% deck Vitesse list they don't burn enough alcohol 00:08:29.210 --> 00:08:29.220 align:start position:0% 00:08:29.220 --> 00:08:31.700 align:start position:0% so<00:08:30.220> that<00:08:30.639> went<00:08:31.120> backwards 00:08:31.700 --> 00:08:31.710 align:start position:0% so that went backwards 00:08:31.710 --> 00:08:33.050 align:start position:0% so that went backwards [Music] 00:08:33.050 --> 00:08:33.060 align:start position:0% [Music] 00:08:33.060 --> 00:08:37.639 align:start position:0% [Music] so<00:08:34.060> where<00:08:34.300> to<00:08:34.479> go<00:08:34.659> from<00:08:34.990> here<00:08:35.250> yeah 00:08:37.639 --> 00:08:37.649 align:start position:0% so where to go from here yeah 00:08:37.649 --> 00:08:40.320 align:start position:0% so where to go from here yeah well<00:08:38.649> then<00:08:38.830> to<00:08:39.279> get<00:08:39.430> from<00:08:39.700> here<00:08:39.909> you<00:08:40.060> have<00:08:40.089> to 00:08:40.320 --> 00:08:40.330 align:start position:0% well then to get from here you have to 00:08:40.330 --> 00:08:43.019 align:start position:0% well then to get from here you have to start<00:08:40.390> doing<00:08:40.750> completely<00:08:41.320> different<00:08:42.070> this<00:08:42.820> is 00:08:43.019 --> 00:08:43.029 align:start position:0% start doing completely different this is 00:08:43.029 --> 00:08:45.329 align:start position:0% start doing completely different this is a<00:08:43.060> blown<00:08:43.419> ham<00:08:43.719> I<00:08:43.930> that<00:08:44.200> burns<00:08:44.380> alcohol<00:08:45.100> instead 00:08:45.329 --> 00:08:45.339 align:start position:0% a blown ham I that burns alcohol instead 00:08:45.339 --> 00:08:47.000 align:start position:0% a blown ham I that burns alcohol instead of<00:08:45.640> gasoline 00:08:47.000 --> 00:08:47.010 align:start position:0% of gasoline 00:08:47.010 --> 00:08:50.250 align:start position:0% of gasoline and<00:08:48.010> these<00:08:48.370> are<00:08:48.640> ideas<00:08:49.270> on<00:08:49.510> the<00:08:49.660> table<00:08:50.110> we're 00:08:50.250 --> 00:08:50.260 align:start position:0% and these are ideas on the table we're 00:08:50.260 --> 00:08:52.949 align:start position:0% and these are ideas on the table we're gonna<00:08:50.320> work<00:08:50.680> with<00:08:51.450> first<00:08:52.450> just<00:08:52.779> some 00:08:52.949 --> 00:08:52.959 align:start position:0% gonna work with first just some 00:08:52.959 --> 00:08:55.590 align:start position:0% gonna work with first just some fine-tuning<00:08:53.520> right<00:08:54.520> now<00:08:54.760> we're<00:08:55.029> using<00:08:55.060> the 00:08:55.590 --> 00:08:55.600 align:start position:0% fine-tuning right now we're using the 00:08:55.600 --> 00:09:00.180 align:start position:0% fine-tuning right now we're using the boost<00:08:55.870> library<00:08:56.970> for<00:08:57.970> the<00:08:58.089> 256<00:08:59.080> bit<00:08:59.350> arithmetic 00:09:00.180 --> 00:09:00.190 align:start position:0% boost library for the 256 bit arithmetic 00:09:00.190 --> 00:09:04.070 align:start position:0% boost library for the 256 bit arithmetic it's<00:09:00.970> really<00:09:01.600> designed<00:09:02.110> for<00:09:02.410> much<00:09:02.860> bigger 00:09:04.070 --> 00:09:04.080 align:start position:0% it's really designed for much bigger 00:09:04.080 --> 00:09:07.850 align:start position:0% it's really designed for much bigger arithmetic<00:09:05.080> so<00:09:05.770> right<00:09:06.130> now<00:09:06.370> it's<00:09:06.670> using<00:09:06.880> five 00:09:07.850 --> 00:09:07.860 align:start position:0% arithmetic so right now it's using five 00:09:07.860 --> 00:09:10.160 align:start position:0% arithmetic so right now it's using five 64-bit<00:09:08.860> words 00:09:10.160 --> 00:09:10.170 align:start position:0% 64-bit words 00:09:10.170 --> 00:09:14.400 align:start position:0% 64-bit words to<00:09:11.170> do<00:09:11.380> just<00:09:11.830> for<00:09:12.490> 64-bit<00:09:13.420> words<00:09:13.690> for<00:09:14.260> the 00:09:14.400 --> 00:09:14.410 align:start position:0% to do just for 64-bit words for the 00:09:14.410 --> 00:09:16.800 align:start position:0% to do just for 64-bit words for the verythe<00:09:14.740> mid-kick<00:09:15.220> so<00:09:16.000> I'm<00:09:16.149> gonna<00:09:16.330> look<00:09:16.540> at 00:09:16.800 --> 00:09:16.810 align:start position:0% verythe mid-kick so I'm gonna look at 00:09:16.810 --> 00:09:20.730 align:start position:0% verythe mid-kick so I'm gonna look at the<00:09:17.230> GMP<00:09:18.089> library<00:09:19.089> which<00:09:19.870> we'll<00:09:20.110> use<00:09:20.290> just<00:09:20.320> for 00:09:20.730 --> 00:09:20.740 align:start position:0% the GMP library which we'll use just for 00:09:20.740 --> 00:09:22.710 align:start position:0% the GMP library which we'll use just for it's<00:09:21.640> written<00:09:22.060> in<00:09:22.150> assembly<00:09:22.690> language 00:09:22.710 --> 00:09:22.720 align:start position:0% it's written in assembly language 00:09:22.720 --> 00:09:25.980 align:start position:0% it's written in assembly language instead<00:09:23.620> of<00:09:23.770> C<00:09:24.100> and<00:09:24.430> we'll<00:09:25.089> see<00:09:25.360> if<00:09:25.510> we<00:09:25.660> can<00:09:25.839> do 00:09:25.980 --> 00:09:25.990 align:start position:0% instead of C and we'll see if we can do 00:09:25.990 --> 00:09:29.250 align:start position:0% instead of C and we'll see if we can do better<00:09:26.020> with<00:09:26.800> that<00:09:27.100> if<00:09:27.760> nothing<00:09:28.330> else<00:09:28.510> those 00:09:29.250 --> 00:09:29.260 align:start position:0% better with that if nothing else those 00:09:29.260 --> 00:09:32.280 align:start position:0% better with that if nothing else those four<00:09:29.770> words<00:09:30.130> will<00:09:30.580> line<00:09:30.850> up<00:09:30.880> on<00:09:31.420> cache<00:09:31.930> line 00:09:32.280 --> 00:09:32.290 align:start position:0% four words will line up on cache line 00:09:32.290 --> 00:09:38.870 align:start position:0% four words will line up on cache line boundaries<00:09:32.950> and<00:09:33.250> that's<00:09:33.430> always<00:09:34.180> good<00:09:34.810> and 00:09:38.870 --> 00:09:38.880 align:start position:0% 00:09:38.880 --> 00:09:42.060 align:start position:0% 64-bit<00:09:39.880> arithmetic<00:09:40.870> we've<00:09:41.230> got<00:09:41.470> to<00:09:41.650> get<00:09:41.830> some 00:09:42.060 --> 00:09:42.070 align:start position:0% 64-bit arithmetic we've got to get some 00:09:42.070 --> 00:09:45.769 align:start position:0% 64-bit arithmetic we've got to get some op<00:09:42.279> codes<00:09:42.640> for<00:09:43.300> 64-bit<00:09:44.140> arithmetic<00:09:44.950> because 00:09:45.769 --> 00:09:45.779 align:start position:0% op codes for 64-bit arithmetic because 00:09:45.779 --> 00:09:49.170 align:start position:0% op codes for 64-bit arithmetic because calendars<00:09:46.920> especially<00:09:47.970> nobody's<00:09:48.970> gonna 00:09:49.170 --> 00:09:49.180 align:start position:0% calendars especially nobody's gonna 00:09:49.180 --> 00:09:51.000 align:start position:0% calendars especially nobody's gonna count<00:09:49.540> to<00:09:49.660> the<00:09:49.870> number<00:09:50.170> of<00:09:50.200> atoms<00:09:50.620> in<00:09:50.950> the 00:09:51.000 --> 00:09:51.010 align:start position:0% count to the number of atoms in the 00:09:51.010 --> 00:09:52.730 align:start position:0% count to the number of atoms in the universe 00:09:52.730 --> 00:09:52.740 align:start position:0% universe 00:09:52.740 --> 00:09:55.710 align:start position:0% universe the<00:09:53.740> interpreter<00:09:54.430> can<00:09:54.459> only<00:09:54.880> make<00:09:55.300> a<00:09:55.330> little 00:09:55.710 --> 00:09:55.720 align:start position:0% the interpreter can only make a little 00:09:55.720 --> 00:09:59.130 align:start position:0% the interpreter can only make a little bit<00:09:56.020> of<00:09:56.050> good<00:09:56.380> use<00:09:56.620> of<00:09:56.650> this<00:09:57.250> but<00:09:57.850> the<00:09:58.029> JIT<00:09:58.420> can 00:09:59.130 --> 00:09:59.140 align:start position:0% bit of good use of this but the JIT can 00:09:59.140 --> 00:10:02.430 align:start position:0% bit of good use of this but the JIT can really<00:09:59.709> really<00:10:00.700> be<00:10:00.880> helped<00:10:01.270> by<00:10:01.510> knowing<00:10:02.079> that 00:10:02.430 --> 00:10:02.440 align:start position:0% really really be helped by knowing that 00:10:02.440 --> 00:10:06.230 align:start position:0% really really be helped by knowing that it's<00:10:02.589> only<00:10:02.800> got<00:10:03.070> 64<00:10:03.700> bits<00:10:03.970> to<00:10:04.180> work<00:10:04.390> with 00:10:06.230 --> 00:10:06.240 align:start position:0% it's only got 64 bits to work with 00:10:06.240 --> 00:10:09.449 align:start position:0% it's only got 64 bits to work with Cindy<00:10:07.240> an<00:10:07.480> awful<00:10:08.140> lot<00:10:08.320> of<00:10:08.350> silicon<00:10:09.070> on<00:10:09.279> the 00:10:09.449 --> 00:10:09.459 align:start position:0% Cindy an awful lot of silicon on the 00:10:09.459 --> 00:10:14.130 align:start position:0% Cindy an awful lot of silicon on the chips<00:10:09.760> right<00:10:10.180> now<00:10:10.450> is<00:10:11.050> Cindy<00:10:11.680> operations<00:10:13.140> and 00:10:14.130 --> 00:10:14.140 align:start position:0% chips right now is Cindy operations and 00:10:14.140 --> 00:10:16.949 align:start position:0% chips right now is Cindy operations and a<00:10:14.320> lot<00:10:14.500> of<00:10:14.529> crypto<00:10:15.040> stuff<00:10:15.430> can<00:10:16.060> take<00:10:16.300> a<00:10:16.329> really 00:10:16.949 --> 00:10:16.959 align:start position:0% a lot of crypto stuff can take a really 00:10:16.959 --> 00:10:20.310 align:start position:0% a lot of crypto stuff can take a really good<00:10:16.990> advantage<00:10:17.620> of<00:10:18.160> Cindy<00:10:18.880> registers<00:10:19.540> so 00:10:20.310 --> 00:10:20.320 align:start position:0% good advantage of Cindy registers so 00:10:20.320 --> 00:10:21.980 align:start position:0% good advantage of Cindy registers so we're<00:10:20.560> looking<00:10:20.950> at<00:10:21.100> that 00:10:21.980 --> 00:10:21.990 align:start position:0% we're looking at that 00:10:21.990 --> 00:10:26.640 align:start position:0% we're looking at that and<00:10:23.070> more<00:10:24.070> structural<00:10:24.910> changes<00:10:25.600> right<00:10:26.290> now 00:10:26.640 --> 00:10:26.650 align:start position:0% and more structural changes right now 00:10:26.650 --> 00:10:30.100 align:start position:0% and more structural changes right now DVM<00:10:27.640> is<00:10:27.880> a<00:10:27.910> stacked<00:10:28.760> if<00:10:29.180> you<00:10:29.420> want<00:10:29.600> to<00:10:29.690> add<00:10:29.810> two 00:10:30.100 --> 00:10:30.110 align:start position:0% DVM is a stacked if you want to add two 00:10:30.110 --> 00:10:33.070 align:start position:0% DVM is a stacked if you want to add two numbers<00:10:30.710> you<00:10:31.520> push<00:10:31.730> a<00:10:31.760> one<00:10:32.090> on<00:10:32.270> the<00:10:32.450> stack<00:10:32.750> you 00:10:33.070 --> 00:10:33.080 align:start position:0% numbers you push a one on the stack you 00:10:33.080 --> 00:10:36.190 align:start position:0% numbers you push a one on the stack you push<00:10:33.590> a<00:10:33.620> two<00:10:33.980> on<00:10:34.250> the<00:10:34.460> stack<00:10:34.760> then<00:10:35.570> you<00:10:35.750> say<00:10:35.990> an 00:10:36.190 --> 00:10:36.200 align:start position:0% push a two on the stack then you say an 00:10:36.200 --> 00:10:39.370 align:start position:0% push a two on the stack then you say an ADD<00:10:36.530> it<00:10:36.950> adds<00:10:37.460> two<00:10:38.000> pulls<00:10:38.630> two<00:10:39.020> of<00:10:39.110> them<00:10:39.260> off 00:10:39.370 --> 00:10:39.380 align:start position:0% ADD it adds two pulls two of them off 00:10:39.380 --> 00:10:41.860 align:start position:0% ADD it adds two pulls two of them off the<00:10:39.560> stack<00:10:39.860> it<00:10:40.430> pushes<00:10:40.880> another<00:10:41.030> one<00:10:41.510> on<00:10:41.720> the 00:10:41.860 --> 00:10:41.870 align:start position:0% the stack it pushes another one on the 00:10:41.870 --> 00:10:43.510 align:start position:0% the stack it pushes another one on the stack<00:10:42.200> and<00:10:42.230> off<00:10:42.680> you<00:10:42.920> go 00:10:43.510 --> 00:10:43.520 align:start position:0% stack and off you go 00:10:43.520 --> 00:10:45.940 align:start position:0% stack and off you go this<00:10:43.910> was<00:10:44.180> like<00:10:44.360> really<00:10:44.780> great<00:10:45.380> for<00:10:45.740> hand 00:10:45.940 --> 00:10:45.950 align:start position:0% this was like really great for hand 00:10:45.950 --> 00:10:48.820 align:start position:0% this was like really great for hand calculators<00:10:46.820> a<00:10:47.120> very<00:10:47.570> good<00:10:48.050> way<00:10:48.260> to<00:10:48.290> do<00:10:48.590> hand 00:10:48.820 --> 00:10:48.830 align:start position:0% calculators a very good way to do hand 00:10:48.830 --> 00:10:52.150 align:start position:0% calculators a very good way to do hand calculators<00:10:49.660> real<00:10:50.660> chips<00:10:51.020> anymore<00:10:51.260> or 00:10:52.150 --> 00:10:52.160 align:start position:0% calculators real chips anymore or 00:10:52.160 --> 00:10:56.460 align:start position:0% calculators real chips anymore or register<00:10:52.880> machines<00:10:53.390> the<00:10:54.320> problem<00:10:54.980> here 00:10:56.460 --> 00:10:56.470 align:start position:0% register machines the problem here 00:10:56.470 --> 00:10:59.560 align:start position:0% register machines the problem here for<00:10:57.470> a<00:10:57.500> chip<00:10:57.890> that's<00:10:58.340> the<00:10:58.550> way<00:10:58.670> you<00:10:58.730> do<00:10:59.060> it<00:10:59.300> but 00:10:59.560 --> 00:10:59.570 align:start position:0% for a chip that's the way you do it but 00:10:59.570 --> 00:11:01.690 align:start position:0% for a chip that's the way you do it but jets<00:10:59.840> tend<00:11:00.140> to<00:11:00.290> run<00:11:00.470> in<00:11:00.650> the<00:11:00.740> background<00:11:00.770> they 00:11:01.690 --> 00:11:01.700 align:start position:0% jets tend to run in the background they 00:11:01.700 --> 00:11:04.660 align:start position:0% jets tend to run in the background they can<00:11:01.940> run<00:11:02.150> slowly<00:11:03.110> so<00:11:03.710> I'm<00:11:03.860> looking<00:11:04.100> basically 00:11:04.660 --> 00:11:04.670 align:start position:0% can run slowly so I'm looking basically 00:11:04.670 --> 00:11:09.010 align:start position:0% can run slowly so I'm looking basically for<00:11:05.510> a<00:11:05.540> very<00:11:05.930> fast<00:11:06.350> order<00:11:07.250> and<00:11:07.490> algorithm<00:11:08.480> to 00:11:09.010 --> 00:11:09.020 align:start position:0% for a very fast order and algorithm to 00:11:09.020 --> 00:11:12.130 align:start position:0% for a very fast order and algorithm to get<00:11:09.290> me<00:11:09.530> from<00:11:09.740> stack<00:11:10.100> code<00:11:10.550> to<00:11:11.240> register<00:11:11.450> code 00:11:12.130 --> 00:11:12.140 align:start position:0% get me from stack code to register code 00:11:12.140 --> 00:11:15.430 align:start position:0% get me from stack code to register code I've<00:11:12.860> done<00:11:13.100> it<00:11:13.220> before<00:11:13.370> for<00:11:14.270> a<00:11:14.300> different<00:11:14.720> VM<00:11:15.080> a 00:11:15.430 --> 00:11:15.440 align:start position:0% I've done it before for a different VM a 00:11:15.440 --> 00:11:17.950 align:start position:0% I've done it before for a different VM a Java<00:11:15.710> VM<00:11:16.190> so<00:11:16.880> I've<00:11:17.000> got<00:11:17.210> to<00:11:17.360> find<00:11:17.570> a<00:11:17.720> way<00:11:17.900> to 00:11:17.950 --> 00:11:17.960 align:start position:0% Java VM so I've got to find a way to 00:11:17.960 --> 00:11:20.790 align:start position:0% Java VM so I've got to find a way to make<00:11:18.320> it<00:11:18.350> work<00:11:18.740> for<00:11:19.100> the<00:11:19.520> EVM 00:11:20.790 --> 00:11:20.800 align:start position:0% make it work for the EVM 00:11:20.800 --> 00:11:22.830 align:start position:0% make it work for the EVM and 00:11:22.830 --> 00:11:22.840 align:start position:0% and 00:11:22.840 --> 00:11:26.080 align:start position:0% and probably<00:11:23.840> would<00:11:24.050> go<00:11:24.260> with<00:11:24.560> just<00:11:25.090> 256 00:11:26.080 --> 00:11:26.090 align:start position:0% probably would go with just 256 00:11:26.090 --> 00:11:28.660 align:start position:0% probably would go with just 256 registers<00:11:26.900> I<00:11:27.410> think<00:11:27.680> that'll<00:11:27.980> be<00:11:28.010> enough<00:11:28.430> for 00:11:28.660 --> 00:11:28.670 align:start position:0% registers I think that'll be enough for 00:11:28.670 --> 00:11:29.790 align:start position:0% registers I think that'll be enough for most<00:11:28.850> purposes 00:11:29.790 --> 00:11:29.800 align:start position:0% most purposes 00:11:29.800 --> 00:11:33.580 align:start position:0% most purposes again<00:11:30.800> I<00:11:31.160> can<00:11:31.460> index<00:11:31.880> them<00:11:32.120> with<00:11:32.270> one<00:11:32.510> byte<00:11:32.840> so 00:11:33.580 --> 00:11:33.590 align:start position:0% again I can index them with one byte so 00:11:33.590 --> 00:11:35.890 align:start position:0% again I can index them with one byte so I<00:11:33.620> don't<00:11:33.890> blow<00:11:34.190> up<00:11:34.370> the<00:11:34.580> code<00:11:34.850> too<00:11:35.180> much<00:11:35.450> and 00:11:35.890 --> 00:11:35.900 align:start position:0% I don't blow up the code too much and 00:11:35.900 --> 00:11:39.370 align:start position:0% I don't blow up the code too much and the<00:11:36.680> code<00:11:36.920> becomes<00:11:37.510> basically<00:11:38.510> three<00:11:38.870> address 00:11:39.370 --> 00:11:39.380 align:start position:0% the code becomes basically three address 00:11:39.380 --> 00:11:42.690 align:start position:0% the code becomes basically three address code<00:11:40.010> so<00:11:40.370> one<00:11:40.610> byte<00:11:40.910> for<00:11:41.210> the<00:11:41.300> operator 00:11:42.690 --> 00:11:42.700 align:start position:0% code so one byte for the operator 00:11:42.700 --> 00:11:45.670 align:start position:0% code so one byte for the operator three<00:11:43.700> bytes<00:11:43.970> for<00:11:44.450> the<00:11:44.510> source<00:11:44.930> the<00:11:45.530> other 00:11:45.670 --> 00:11:45.680 align:start position:0% three bytes for the source the other 00:11:45.680 --> 00:11:48.120 align:start position:0% three bytes for the source the other source<00:11:46.100> and<00:11:46.490> the<00:11:46.760> destination 00:11:48.120 --> 00:11:48.130 align:start position:0% source and the destination 00:11:48.130 --> 00:11:52.210 align:start position:0% source and the destination and<00:11:49.130> that<00:11:49.700> goes<00:11:49.940> backwards<00:11:50.540> but<00:11:50.930> gee<00:11:51.620> I<00:11:51.860> like 00:11:52.210 --> 00:11:52.220 align:start position:0% and that goes backwards but gee I like 00:11:52.220 --> 00:11:56.380 align:start position:0% and that goes backwards but gee I like that<00:11:52.520> I<00:11:52.670> want<00:11:52.940> one<00:11:53.090> of<00:11:53.120> those 00:11:56.380 --> 00:11:56.390 align:start position:0% 00:11:56.390 --> 00:11:59.280 align:start position:0% [Music] 00:11:59.280 --> 00:11:59.290 align:start position:0% [Music] 00:11:59.290 --> 00:12:05.100 align:start position:0% [Music] and 00:12:05.100 --> 00:12:05.110 align:start position:0% 00:12:05.110 --> 00:12:08.820 align:start position:0% that's<00:12:06.110> that<00:12:06.520> who's<00:12:07.520> next 00:12:08.820 --> 00:12:08.830 align:start position:0% that's that who's next 00:12:08.830 --> 00:12:12.740 align:start position:0% that's that who's next [Applause] 00:12:12.740 --> 00:12:12.750 align:start position:0% [Applause] 00:12:12.750 --> 00:12:21.980 align:start position:0% [Applause] [Music]