Derek Schuff c767cbf942 [MC] Attach labels to existing fragments instead of using a separate fragment ... Summary: Currently when emitting a label, a new data fragment is created for it if the current fragment isn't a data fragment. This change instead enqueues the label and attaches it to the next fragment (e.g. created for the next instruction) if possible. When bundle alignment is not enabled, this has no functionality change (it just results in fewer extra fragments being created). For bundle alignment, previously labels would point to the beginning of the bundle padding instead of the beginning of the emitted instruction. This was not only less efficient (e.g. jumping to the nops instead of past them) but also led to miscalculation of the address of the GOT (since MC uses a label difference rather than emitting a "." symbol). Fixes https://code.google.com/p/nativeclient/issues/detail?id=3982 Test Plan: regression test attached Reviewers: jvoung, eliben Subscribers: jfb, llvm-commits Differential Revision: http://reviews.llvm.org/D5915 llvm-svn: 220439		2014-10-22 22:38:06 +00:00
..
align-mode-argument-error.s
asm-printing-bundle-directives.s
autogen-inst-offset-align-to-end.s
autogen-inst-offset-padding.s
bundle-group-too-large-error.s
bundle-lock-option-error.s
different-sections.s
labeloffset.s
lit.local.cfg
lock-without-bundle-mode-error.s
long-nop-pad.s
nesting.s
pad-align-to-bundle-end.s
pad-bundle-groups.s
relax-at-bundle-end.s
relax-in-bundle-group.s
single-inst-bundling.s
switch-section-locked-error.s
unlock-without-lock-error.s