Update docs on filling text with nops.

gas/
	* doc/as.texinfo (.align): Change some to most for text nop fill.
	(.balign, .p2align): Likewise.
This commit is contained in:
Jim Wilson 2017-11-22 11:09:30 -08:00
parent fc35dab1a6
commit 2ca23e65f5
2 changed files with 8 additions and 3 deletions

View File

@ -1,3 +1,8 @@
2017-11-22 Jim Wilson <jimw@sifive.com>
* doc/as.texinfo (.align): Change some to most for text nop fill.
(.balign, .p2align): Likewise.
2017-11-22 Thomas Preud'homme <thomas.preudhomme@arm.com>
* config/tc-arm.c (arm_reg_type): Comment on the link with

View File

@ -4606,7 +4606,7 @@ required, as described below.
The second expression (also absolute) gives the fill value to be stored in the
padding bytes. It (and the comma) may be omitted. If it is omitted, the
padding bytes are normally zero. However, on some systems, if the section is
padding bytes are normally zero. However, on most systems, if the section is
marked as containing code and the fill value is omitted, the space is filled
with no-op instructions.
@ -4706,7 +4706,7 @@ is already a multiple of 8, no change is needed.
The second expression (also absolute) gives the fill value to be stored in the
padding bytes. It (and the comma) may be omitted. If it is omitted, the
padding bytes are normally zero. However, on some systems, if the section is
padding bytes are normally zero. However, on most systems, if the section is
marked as containing code and the fill value is omitted, the space is filled
with no-op instructions.
@ -6172,7 +6172,7 @@ multiple of 8, no change is needed.
The second expression (also absolute) gives the fill value to be stored in the
padding bytes. It (and the comma) may be omitted. If it is omitted, the
padding bytes are normally zero. However, on some systems, if the section is
padding bytes are normally zero. However, on most systems, if the section is
marked as containing code and the fill value is omitted, the space is filled
with no-op instructions.