2.3 cont. | RISCY BUSINESS Episode Guide

0:08Recap and set the stage for the day with a mention of the addition of @naked to hula¹

3:56Review the addition of "register" to hula²

6:11Show off the hula hello.S asm³

12:15riskyfive By the way, about porting D to RISC-V. I'm stalled on a GCC bug. Exception support in GCC / glibc has a bug, but people from SiFive are working on it

🗪

12:15riskyfive By the way, about porting D to RISC-V. I'm stalled on a GCC bug. Exception support in GCC / glibc has a bug, but people from SiFive are working on it

🗪

12:15riskyfive By the way, about porting D to RISC-V. I'm stalled on a GCC bug. Exception support in GCC / glibc has a bug, but people from SiFive are working on it

🗪

12:49Thoughts on writing asm and architectural and general portability⁴

🗩

12:49Thoughts on writing asm and architectural and general portability⁴

🗩

12:49Thoughts on writing asm and architectural and general portability⁴

🗩

15:43Jump into the book

🗩

15:43Jump into the book

🗩

15:43Jump into the book

🗩

16:50Compiling an Assignment When an Operand Is in Memory⁵

🖌

16:50Compiling an Assignment When an Operand Is in Memory⁵

🖌

16:50Compiling an Assignment When an Operand Is in Memory⁵

🖌

19:25Our answer to Chapter 2.3 'Compiling an Assignment When an Operand Is in Memory'⁶

🖌

19:25Our answer to Chapter 2.3 'Compiling an Assignment When an Operand Is in Memory'⁶

🖌

19:25Our answer to Chapter 2.3 'Compiling an Assignment When an Operand Is in Memory'⁶

🖌

20:33Chapter 2.3 continued, Hardware / Software Interface⁷

23:09Figure 2.3 Actual RISC-V memory addresses and contents of memory for those doublewords

🖌

23:09Figure 2.3 Actual RISC-V memory addresses and contents of memory for those doublewords

🖌

23:09Figure 2.3 Actual RISC-V memory addresses and contents of memory for those doublewords

🖌

23:54Chapter 2.3 continued⁸

24:30Endianness, with a fun fact: It's a reference to Gulliver's Travels

🗩

24:30Endianness, with a fun fact: It's a reference to Gulliver's Travels

🗩

24:30Endianness, with a fun fact: It's a reference to Gulliver's Travels

🗩

25:56Chapter 2.3 continued⁹

26:39riskyfive We should write things on paper little endian style

🗪

26:39riskyfive We should write things on paper little endian style

🗪

26:39riskyfive We should write things on paper little endian style

🗪

27:07Thoughts on "endianness" in RTL vs LTR languages

🗩

27:07Thoughts on "endianness" in RTL vs LTR languages

🗩

27:07Thoughts on "endianness" in RTL vs LTR languages

🗩

29:20riskyfive Yes, yes, that's the reasoning that'll eventually convince you that we should change to little endian on paper. Let the endianness flow through you. Come to the little side of the force

🗪

29:20riskyfive Yes, yes, that's the reasoning that'll eventually convince you that we should change to little endian on paper. Let the endianness flow through you. Come to the little side of the force

🗪

29:20riskyfive Yes, yes, that's the reasoning that'll eventually convince you that we should change to little endian on paper. Let the endianness flow through you. Come to the little side of the force

🗪

29:48Chapter 2.3 continued¹⁰

31:21Thoughts on asm syntax, with a mention of Per's chosen syntax for his assembler

🖌

31:21Thoughts on asm syntax, with a mention of Per's chosen syntax for his assembler

🖌

31:21Thoughts on asm syntax, with a mention of Per's chosen syntax for his assembler

🖌

34:52Chapter 2.3 continued¹¹

37:12Thoughts on alignment of memory accesses

🗩

37:12Thoughts on alignment of memory accesses

🗩

37:12Thoughts on alignment of memory accesses

🗩

38:35riskyfive Got to go. Good night!

🗪

38:35riskyfive Got to go. Good night!

🗪

38:35riskyfive Got to go. Good night!

🗪

38:44On RISC-V's ability to do unaligned memory accesses

🗩

38:44On RISC-V's ability to do unaligned memory accesses

🗩

38:44On RISC-V's ability to do unaligned memory accesses

🗩

39:54Chapter 2.3 continued, Hardware / Software Interface¹²

40:35Thoughts on the marketing of hard drive and memory capacities, and confusion of units

🗩

40:35Thoughts on the marketing of hard drive and memory capacities, and confusion of units

🗩

40:35Thoughts on the marketing of hard drive and memory capacities, and confusion of units

🗩

44:50Chapter 2.3 Example 3 - Compiling Using Load and Store¹³

45:26A[12] = h + A[8];

🖌

45:26A[12] = h + A[8];

🖌

45:26A[12] = h + A[8];

🖌

53:24Compare our answer to Chapter 2.3 Example 3 with the book¹⁴

55:33Thoughts on calling conventions

🗩

55:33Thoughts on calling conventions

🗩

55:33Thoughts on calling conventions

🗩

1:01:27Continue to compare our answer to Chapter 2.3 Example 3 with the book,¹⁵ with thoughts on destructive operations

1:09:01Chapter 2.3 continued, Hardware / Software Interface¹⁶

1:09:21The stack

🗩

1:09:21The stack

🗩

1:09:21The stack

🗩

1:13:18Chapter 2.3 continued, Hardware / Software Interface¹⁷

1:13:45Using saved registers and temporaries, and the concept of spilling to the stack

🗩

1:13:45Using saved registers and temporaries, and the concept of spilling to the stack

🗩

1:13:45Using saved registers and temporaries, and the concept of spilling to the stack

🗩

1:16:39Chapter 2.3 continued, Hardware / Software Interface¹⁸

1:18:08Chapter 2.3 Elaboration¹⁹

1:18:48Hierarchy of Caches

🗩

1:18:48Hierarchy of Caches

🗩

1:18:48Hierarchy of Caches

🗩

1:22:09Chapter 2.3 - Constant or Immediate Operands²⁰

1:25:24Chapter 2.3 - Check Yourself²¹

1:26:29Virtual vs actual registers

🗩

1:26:29Virtual vs actual registers

🗩

1:26:29Virtual vs actual registers

🗩

1:29:39Our answer to Chapter 2.3 - Check Yourself²²

1:30:58Chapter 2.3 Check Yourself Answer²³

1:32:35Chapter 2.3 Elaborations on registers²⁴

1:36:32C type widths, and data models²⁵

🗩

1:36:32C type widths, and data models²⁵

🗩

1:36:32C type widths, and data models²⁵

🗩

1:41:24Show type-width handling in nwr_mem.h

1:46:45Chapter 2.3 Elaborations on registers, continued²⁶

1:49:03Show size_t use in pcalc's linux_x86_64.c

1:51:14Chapter 2.3 Elaborations on registers, continued²⁷

1:52:19That is the end of 2.3, with a glimpse into the next chapter

🗩

1:52:19That is the end of 2.3, with a glimpse into the next chapter

🗩

1:52:19That is the end of 2.3, with a glimpse into the next chapter

🗩

1:53:52Considering the benefits of C over assembly: portability, automatic handling of calling conventions, and…

🗩

1:53:52Considering the benefits of C over assembly: portability, automatic handling of calling conventions, and…

🗩

1:53:52Considering the benefits of C over assembly: portability, automatic handling of calling conventions, and…

🗩

1:57:57The other major benefit of C over assembly, along with portability, is that it is a structured language

🗩

1:57:57The other major benefit of C over assembly, along with portability, is that it is a structured language

🗩

1:57:57The other major benefit of C over assembly, along with portability, is that it is a structured language

🗩

2:06:49End the episode, with shout-outs to new supporters

🗩

2:06:49End the episode, with shout-outs to new supporters

🗩

2:06:49End the episode, with shout-outs to new supporters

🗩

RISCY BUSINESS

Keyboard Navigation

Global Keys

Menu toggling

In-Menu Movement

Quotes and References Menus

Quotes, References and Credits Menus

Filter Menu

Filter and Link Menus

Credits Menu