[PATCH v2 RESEND] Document .Nbyte assembler directives

[Nick Clifton]

Hi Richard,

> Why zero or more?

No idea - maybe it was so that gcc could generate these directives without
having to check that there always was a value to be generated ?

> What happens if there are zero expressions?  Do I get
> a single entry inserted (with what), or nothing?
> 
> I think it's also worth pointing out that these:
> - Don't align (even if .short, .word, etc would)
> - Might affect the choice of relocation in a target-dependent manner.
> - Follow the natural endian model for the target (sort of expected, but
> probably worth stating anyway).
> 
> Given the above, it might be worth reworking this so that all three
> directives come in a single block with a common description; or put all
> the information in the first and reference it in the subsequent entries.

Is this what you had in mind:

Cheers
  Nick

-------------- next part --------------
A non-text attachment was scrubbed...
Name: as.texinfo.patch
Type: text/x-patch
Size: 2772 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/binutils/attachments/20170320/d333ce4a/attachment.bin>