Awesome Contents

Pure & Utter Insanity (Dhrystone)

Pure & Utter Insanity (Dhrystone) ⚠ Click here to regain focus ⚠
?
?

Keyboard Navigation

Global Keys

W, A, P / S, D, N Jump to previous / next marker
z Toggle filter mode V Revert filter to original state

Menu toggling

q Quotes r References f Filter c Credits

Movement

a
w
s
d
h j k l


Quotes and References Menus

Enter Jump to timecode

Quotes, References and Credits Menus

o Open URL (in new tab)

Filter Menu

x, Space Toggle category and focus next
X, ShiftSpace Toggle category and focus previous
v Invert topics / media as per focus

Credits Menu

Enter Open URL (in new tab)
0:07Recap with a few words on the pronunciation of Dhrystone1
0:07Recap with a few words on the pronunciation of Dhrystone1
0:07Recap with a few words on the pronunciation of Dhrystone1
2:25Reflect on the unimpressive nature of synthetic benchmarks
2:25Reflect on the unimpressive nature of synthetic benchmarks
2:25Reflect on the unimpressive nature of synthetic benchmarks
4:14Study the procedures in dhry_1.c
4:14Study the procedures in dhry_1.c
4:14Study the procedures in dhry_1.c
8:27Study Func_2() and Func_1() in dhry_2.c
8:27Study Func_2() and Func_1() in dhry_2.c
8:27Study Func_2() and Func_1() in dhry_2.c
20:15Consult the documentation on strcmp()2
20:15Consult the documentation on strcmp()2
20:15Consult the documentation on strcmp()2
22:05Continue studying Func_2() in dhry_2.c
22:05Continue studying Func_2() in dhry_2.c
22:05Continue studying Func_2() in dhry_2.c
23:24Try to establish which strcpy() and strcmp() we are using
23:24Try to establish which strcpy() and strcmp() we are using
23:24Try to establish which strcpy() and strcmp() we are using
31:42croepha Hey Buddy
31:42croepha Hey Buddy
31:42croepha Hey Buddy
31:46Read strcmp.c and strcpy.c
31:46Read strcmp.c and strcpy.c
31:46Read strcmp.c and strcpy.c
33:15Return to dhry_1.c and determine that the comments may come from the original, 1-indexed Ada implementation
33:15Return to dhry_1.c and determine that the comments may come from the original, 1-indexed Ada implementation
33:15Return to dhry_1.c and determine that the comments may come from the original, 1-indexed Ada implementation
35:17Read Proc_7() and Proc_8() in dhry_2.c
35:17Read Proc_7() and Proc_8() in dhry_2.c
35:17Read Proc_7() and Proc_8() in dhry_2.c
42:46Read Proc_1() in dhry_1.c
42:46Read Proc_1() in dhry_1.c
42:46Read Proc_1() in dhry_1.c
45:36Read Proc_3() in dhry_1.c
45:36Read Proc_3() in dhry_1.c
45:36Read Proc_3() in dhry_1.c
48:35Return to Proc_1() in dhry_1.c, after the call to Proc_3()
48:35Return to Proc_1() in dhry_1.c, after the call to Proc_3()
48:35Return to Proc_1() in dhry_1.c, after the call to Proc_3()
49:33Read Proc_6() in dhry_2.c
49:33Read Proc_6() in dhry_2.c
49:33Read Proc_6() in dhry_2.c
51:16This is just bananacakes
51:16This is just bananacakes
51:16This is just bananacakes
51:36croepha It wasn't me, but I am a mad man
51:36croepha It wasn't me, but I am a mad man
51:36croepha It wasn't me, but I am a mad man
52:03Read Func_3() in dhry_2.c
52:03Read Func_3() in dhry_2.c
52:03Read Func_3() in dhry_2.c
52:36croepha It depends on what you mean, I might be worse. I do things with macros that would probably drive you crazy. I also make code generators
52:36croepha It depends on what you mean, I might be worse. I do things with macros that would probably drive you crazy. I also make code generators
52:36croepha It depends on what you mean, I might be worse. I do things with macros that would probably drive you crazy. I also make code generators
53:21Continue to read Proc_6() and Func_3() in dhry_2.c
53:21Continue to read Proc_6() and Func_3() in dhry_2.c
53:21Continue to read Proc_6() and Func_3() in dhry_2.c
54:30Finish reading Proc_1()
54:30Finish reading Proc_1()
54:30Finish reading Proc_1()
55:12Wonder if this program was carefully crafted to exercise the instructions well, and to confuse the compiler
55:12Wonder if this program was carefully crafted to exercise the instructions well, and to confuse the compiler
55:12Wonder if this program was carefully crafted to exercise the instructions well, and to confuse the compiler
56:52Try to reorient ourselves
56:52Try to reorient ourselves
56:52Try to reorient ourselves
57:54croepha /me goes off to try some of this syntax
57:54croepha /me goes off to try some of this syntax
57:54croepha /me goes off to try some of this syntax
57:56A few words on the old-style C code
57:56A few words on the old-style C code
57:56A few words on the old-style C code
1:00:22croepha Does that compile for you?
1:00:22croepha Does that compile for you?
1:00:22croepha Does that compile for you?
1:03:08Continue to read through the main timing loop in dhry_1.c
1:03:08Continue to read through the main timing loop in dhry_1.c
1:03:08Continue to read through the main timing loop in dhry_1.c
1:05:02Read Proc_2() in dhry_1.c
1:05:02Read Proc_2() in dhry_1.c
1:05:02Read Proc_2() in dhry_1.c
1:06:53Scan through the statistical printing code in dhry_1.c
1:06:53Scan through the statistical printing code in dhry_1.c
1:06:53Scan through the statistical printing code in dhry_1.c
1:07:46Reflect on our experience investigating this demo
1:07:46Reflect on our experience investigating this demo
1:07:46Reflect on our experience investigating this demo
1:08:45We are out of time, with a note that we ought to update the Freedom E SDK
1:08:45We are out of time, with a note that we ought to update the Freedom E SDK
1:08:45We are out of time, with a note that we ought to update the Freedom E SDK
1:10:17croepha Are you excited about any other [sic] RISC-V chips? Any comments on the privileged mode instruction spec draft?
1:10:17croepha Are you excited about any other [sic] RISC-V chips? Any comments on the privileged mode instruction spec draft?
1:10:17croepha Are you excited about any other [sic] RISC-V chips? Any comments on the privileged mode instruction spec draft?
1:12:18Point out lowRISC3
1:12:18Point out lowRISC3
1:12:18Point out lowRISC3
1:13:54Thank you
1:13:54Thank you
1:13:54Thank you