TheCloud/rvalp
1
0
Fork 0
mirror of https://github.com/johnwinans/rvalp.git synced 2025-09-29 14:11:14 -04:00
Code Issues Packages Projects Releases Wiki Activity

Wording and format cleanup.

Browse Source
This commit is contained in:
John Winans 2020-03-11 10:47:31 -05:00
parent 70d9744528
commit b27517cef8
1 changed files with 26 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

58
book/programs/chapter.tex
View File

@ -94,14 +94,18 @@ can never store a value into the x0 register.)
The RISC-V assembler provides a pseudoinstruction specifically for this The RISC-V assembler provides a pseudoinstruction specifically for this
purpose that you can use to improve the readability of your code. Note purpose that you can use to improve the readability of your code. Note
that the \insn{addi} and \insn{nop} instructions in \listingRef{nop/nop.S} that the \insn{addi} and \insn{nop} instructions in \listingRef{nop/nop.S}
are assembled into the exact same binary machine instruction (The are assembled into the exact same binary machine instructions
\hex{00000013} you can see are stored at addresses \hex{0} and \hex{4}) as can be seen by comparing it to
as seen by looking at the objdump listing in \listingRef{nop/nop.lst}. \verb@objdump@ \listingRef{nop/nop.lst},
In fact, you can see that objdump shows both instructions as a \insn{nop} and \verb@rvddt@ \listingRef{nop/nop.out} output.
while \listingRef{nop/nop.out} shows that \rvddt{} displays both as
\verb@addi x0, x0, 0@.
\listing{nop/nop.S}{Demonstrate that an \insn{addi} can be the same as \insn{nop}.} %(The \hex{00000013} you can see are stored at addresses \hex{0} and \hex{4})
%as seen by looking at the \verb@objdump@ listing in \listingRef{nop/nop.lst}.
%In fact, you can see that objdump shows both instructions as a \insn{nop}
%while \listingRef{nop/nop.out} shows that \rvddt{} displays both as
%\verb@addi x0, x0, 0@.
\listing{nop/nop.S}{Demonstrate that \insn{addi} can be used as a \insn{nop}.}
\index{objdump} \index{objdump}
\listing{nop/nop.lst}{Using \insn{addi} to perform a \insn{nop}} \listing{nop/nop.lst}{Using \insn{addi} to perform a \insn{nop}}
@ -183,7 +187,6 @@ For example, to set \reg{t3} to zero:
addi rd, rs, 0 # copy reg rs to rd (pseudo: mv rd, rs) addi rd, rs, 0 # copy reg rs to rd (pseudo: mv rd, rs)
\end{verbatim} \end{verbatim}
Demonstrate various addi instructions.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@ -204,7 +207,6 @@ Ideas for the order of introducing instructions.
\label{uguide:slli} \label{uguide:slli}
\label{uguide:srli} \label{uguide:srli}
\begin{verbatim} \begin{verbatim}
addi
andi andi
ori ori
xori xori
@ -248,8 +250,6 @@ Copying values from a register to memory:
sw sw
\end{verbatim} \end{verbatim}
\enote{Mention the rvddt UART I/O address for writing to the console here?}
\section{RR operations} \section{RR operations}
\label{uguide:add} \label{uguide:add}
\label{uguide:sub} \label{uguide:sub}
@ -338,29 +338,35 @@ Start to introduce addressing here?
\section{Relocation} \section{Relocation}
\begin{verbatim}
Absolute: Absolute:
\begin{verbatim}
%hi(symbol) %hi(symbol)
%lo(symbol) %lo(symbol)
\end{verbatim}
PC-relative: PC-relative:
\begin{verbatim}
%pcrel_hi(symbol) %pcrel_hi(symbol)
%pcrel_lo(label) %pcrel_lo(label)
\end{verbatim}
Using the auipc & addi pair with label references: Using \verb@auipc@ \& \verb@addi@ together with label references:
The %pcrel_lo() uses the label to find the associated %pcrel_hi()
The label MUST be on a line that used a %pcrel_hi() or get an error. The \verb@%pcrel_lo()@ uses the label to find the associated \verb@%pcrel_hi()@.
This is needed to calculate the proper offset. The label MUST be on a line that used a \verb@%pcrel_hi()@ or get an error.
Things like this are legal (though not sure of the value): This is needed to calculate the proper offset.
label: auipc t1, %pcrel_hi(symbol)
Things like this are legal:
\begin{verbatim}
label: auipc t1, %pcrel_hi(symbol)
addi t2, t1, %pcrel_lo(label) addi t2, t1, %pcrel_lo(label)
addi t3, t1, %pcrel_lo(label) addi t3, t1, %pcrel_lo(label)
lw t4, %pcrel_lo(label)(t1) lw t4, %pcrel_lo(label)(t1)
sw t5, %pcrel_lo(label)(t1) sw t5, %pcrel_lo(label)(t1)
\end{verbatim}
Discuss how relaxation works. Discuss how relaxation works.
see: https://github.com/riscv/riscv-elf-psabi-doc/blob/master/riscv-elf.md see: \url{https://github.com/riscv/riscv-elf-psabi-doc/blob/master/riscv-elf.md}
\end{verbatim}
\section{Jumps} \section{Jumps}
@ -406,15 +412,3 @@ Introduce and present subroutines but not nesting until introduce stack operatio
jalr x0, x6, offset[11:0] jalr x0, x6, offset[11:0]
\end{verbatim} \end{verbatim}
\section{The Linker and Relaxation}
\enote{Needs research.
I'm not sure if/how the linker alone can relax the AUIPC+JALR pair since
the assembler could have used a pcrel branch across one of these pairs.}%
I don't know where this should go just yet.
\section{pic and nopic}
pic is {\em needed} for shared libs. Should discuss it but probably best
to leave the topic for a later chapter.