Clarify volatility of VSRs that overlap FPRs

Fixes #99.

Signed-off-by: Bill Schmidt <wschmidt@linux.ibm.com>
master
Bill Schmidt 5 years ago
parent 3b979cc112
commit 806af64bc3

@ -5027,7 +5027,11 @@ xml:id="dbdoclet.50655240_pgfId-1156194">
revisionflag="changed">least-significant halves of those VSX revisionflag="changed">least-significant halves of those VSX
registers corresponding</phrase> to the classic floating-point registers corresponding</phrase> to the classic floating-point
registers (that is, vsr0&#8211;vsr31), <phrase registers (that is, vsr0&#8211;vsr31), <phrase
revisionflag="changed">are</phrase> volatile.</para> revisionflag="changed">are</phrase> volatile. <phrase
revisionflag="added">If the most-significant half of such a
VSX register is a non-volatile floating-point register that is
not used for a function call, the entire VSX register is
volatile.</phrase></para>


<table frame="all" pgwide="1" xml:id="dbdoclet.50655240_83567"> <table frame="all" pgwide="1" xml:id="dbdoclet.50655240_83567">
<title>Floating-Point Register Roles for Binary Floating-Point <title>Floating-Point Register Roles for Binary Floating-Point

Loading…
Cancel
Save