Add a test to expose the gc-section assertion issue.

The expected output from this command is what I think we should be
getting, but it might turn out that when the assertion is fixed the
expected output will need to be tweaked a little.  Currently this new
test fails with an assertion.
Turn on gc-sections, and fix bug causing an assert to fire.

When processing relocations of type R_ARC_32, R_ARC_32_ME, and
R_ARC_PC32, and we're creating a shared library, then relocations to
global symbols are maintained in the final output ELF, but relocations
to local symbols are resolved immediately.

The "if ... " condition modified in this patch is responsible for
deciding if a relocation is to a local symbol that should be resolved
immediately, if not the relocation is assumed to be for a global symbol.

The bug fixed here is that a symbol which would have otherwise been
global, is being forced local due to a version script, as such the
symbol should be handled as a local symbol, however, it has /some/ of
the characteristics of a global symbol, the code previously,
incorrectly, thought that the symbol was global when it should have been
treating it as local.

bfd/ChangeLog:

	* elf32-arc.c (elf_arc_relocate_section): Handle symbols that have
	been forced local immediately, update the comment associated.
        (elf_backend_can_gc_sections): Allow gc-sections.
Merge pull request #2 from T-J-Teru/gc-sections

Turn on gc-sections support.