From 2c052b1ec5a5e2c51989eb109f8559a9df6d8202 Mon Sep 17 00:00:00 2001 From: Bill Schmidt Date: Tue, 1 Dec 2020 11:25:46 -0600 Subject: [PATCH] Remove "note" markup from section 2.3.5 This markup was causing overflow into the footer, and marking this as a note was really unnecessary, so this is not a substantive change. Signed-off-by: Bill Schmidt --- specification/ch_2.xml | 8 -------- 1 file changed, 8 deletions(-) diff --git a/specification/ch_2.xml b/specification/ch_2.xml index bb699e8..abc2aa2 100644 --- a/specification/ch_2.xml +++ b/specification/ch_2.xml @@ -7751,9 +7751,6 @@ stw r9, 0(r11) - - - Due to fusion hardware support, the preferred code forms are destructive Destructive in this context refers to a code sequence where @@ -7766,8 +7763,6 @@ stw r9, 0(r11) high-order bits followed immediately by a destructive load using the same target register as the addis instruction to load data from a signed 32-bit offset from a base register. - - For TOC-based PIC code (see and ), the offset in the @@ -7829,9 +7824,6 @@ stw r9, 0(r11) If it has an unsigned immediate operand (for example, ori), use symbol@got@h. For a description of high-adjusted values, see . - - -
Function Calls