+2017-03-11 Alan Modra <amodra@gmail.com>
+
+ * ld.texinfo (Orphan Sections): Mention that not all targets
+ handle orphans well.
+ * testsuite/ld-elf/orphan-9.d: Don't run for i860 and i960.
+ * testsuite/ld-elf/orphan-10.d: Likewise.
+
2017-03-09 Andrew Burgess <andrew.burgess@embecosm.com>
* ldlang.c (lang_size_sections_1): Shortcut loop only after
If new output sections are created to hold orphaned input sections,
then the linker must decide where to place these new output sections
-in relation to existing output sections. The linker uses a simple
-heuristic to do this. It attempts to place orphan sections after
-sections of the same attribute, such as code vs data, loadable vs
-non-loadable, etc. If no sections with matching attributes are found,
-the orphan section is placed at the end of the file.
-
-For ELF targets, the attribute of the section includes section type as
-well as section flag.
+in relation to existing output sections. On most modern targets, the
+linker attempts to place orphan sections after sections of the same
+attribute, such as code vs data, loadable vs non-loadable, etc. If no
+sections with matching attributes are found, or your target lacks this
+support, the orphan section is placed at the end of the file.
The command line options @samp{--orphan-handling} and @samp{--unique}
(@pxref{Options,,Command Line Options}) can be used to control which