> "run-time", according to my reading of > http://gcc.gnu.org/codingconventions.html .
I chenged it, but I note that "runtime" is used much more often than "run-time" and "run time" in the docs. However, "runtime" is preferred for "libraries and system support present at run time", which is what this option controls. > Here I am wondering whether to simply omit "instead of decimal"? (If > not, somehow that part of the sentence comes across as a bit odd, but > then I'm not a native speaker.) New text: Force assembly output to always use hex constants. Normally such constants are signed decimals, but this option is available for testsuite and/or aesthetic purposes. > What are the other legitimate options beyond these two? We're still discussing that with TI; historical non-fsf versions of the msp-gcc allow the full chip number here (i.e. msp430F5438). Ideally, such would still be allowed, but the community is talking about switching to -mcpu= for the ISA and using -mmcu= only for the linker scripts. For now, we allow chip numbers but only look for the 'x' to determine the ISA. We might allow for arbitrary chip numbers, to be passed to the assembler/linker or to be used as filenames for linker scripts, headers, or libraries. So, I only documented the use I know is currently supported. > > +@item -mrelax > > +@opindex mrelax > > +Perform link-time opcode relaxing. > > Will everyone know what opcode relaxing is? New text: This option is passed to the assembler and linker, and allows the linker to perform certain optimizations that cannot be done until the final link. > "restricted 64k range of constants", what's that? And kBit or kByte? New text: Memory references which do not require an extended MOVX instruction. > The doc changes look fine modulo the above, and I assume you'll want > to add a note to the release notes htdocs/gcc-4.9/changes.html and a > news item to htdocs/index.html . I included index.html, I thought... I didn't see changes.html in the file list I had, though, but I can certainly add that too.
