stomache MCAsmInfo having this, and I found a better solution to
this layering issue.

llvm-svn: 93985

more cases where debug declarations affect
debug line info.

llvm-svn: 93953

llvm-svn: 93940

line number info.

llvm-svn: 93937

I really want clients of the streamer to be able to say "emit this
64-bit integer" and have it get broken down right by the streamer.

I may change this in the future, we'll see how it works out.

llvm-svn: 93934

llvm-svn: 93918

the two token accessor functions are declared consistently.
Modified the clients of MCAsmParser to reflect this change.

llvm-svn: 93916

Since the mov is executed unconditionally, make sure that the add didn't have
any predicate.

llvm-svn: 93909

MCAsmParser, and changed the target-specific AsmParsers
to use it.

llvm-svn: 93900

in use by Mips.

llvm-svn: 93897

identifier.  There is no way to work around it.

llvm-svn: 93896

which we don't support anymore.

llvm-svn: 93886

function can support dynamic stack realignment. That's a much easier question
to answer at instruction selection stage than whether the function actually
will have dynamic alignment prologue. This allows the removal of the
stack alignment heuristic pass, and improves code quality for cases where
the heuristic would result in dynamic alignment code being generated when
it was not strictly necessary.

llvm-svn: 93885

the instruction to load those args removed. This fix PR6071

llvm-svn: 93880

llvm-svn: 93876

llvm-svn: 93875

.zerofill directive.  Streamerize its generation.

llvm-svn: 93868

llvm-svn: 93864

llvm-svn: 93863

doing global variable classification anymore) and hookized, sink almost
all target targets global variable emission code into AsmPrinter and out
of each target.

Some notes:

1. PIC16 does completely custom and crazy stuff, so it is not changed.
2. XCore has some custom handling for extra directives.  I'll look at it next.
3. This switches linux/ppc to use .globl instead of .global.  If .globl is
   actually wrong, let me know and I'll fix it.
4. This makes linux/ppc get a lot of random cases right which were obviously
   wrong before, it is probably now a bit healthier.
5. Blackfin will probably start getting .comm and other things that it didn't
   before.  If this is undesirable, it should explicitly opt out of these
   things by clearing the relevant fields of MCAsmInfo.

This leads to a nice diffstat:
 14 files changed, 127 insertions(+), 830 deletions(-)

llvm-svn: 93858

llvm-svn: 93857

just like all other elf targets.  Bruno, if this isn't right, please
let me know + why :)

llvm-svn: 93856

llvm-svn: 93855

I'm not sure that this is correct, but it causes no test failures,
and just emitting a .comm without protecting its linkage somehow
is surely not right.

llvm-svn: 93854

llvm-svn: 93853

llvm-svn: 93852

This makes a similar code dead in all the other targets, I'll clean it up
in a bit.

This also moves handling of lcomm up before acquisition of a section,
since lcomm never needs a section.

llvm-svn: 93851

darwin into common code.

llvm-svn: 93849

duplicating the logic (differently) in lots of different targets.

llvm-svn: 93847

and everything else (weak).

llvm-svn: 93846

llvm-svn: 93845

GCC would put weak zero initialized mutable data in the .bss section,
we would put it into a crasy '.gnu.linkonce.b.test,"aw",@nobits' 
section.  Fixing this will allow simplifications next up.

llvm-svn: 93844

simplify and commonize some of the asmprinter logic for globals.

This also avoids printing the MCSection for .zerofill, which broke
the llvm-gcc build.

llvm-svn: 93843

llvm-svn: 93841

llvm-svn: 93839

1. TargetLoweringObjectFileMachO should decide if something
   goes in zerofill instead of having every target do it.
2. TargetLoweringObjectFileMachO should assign said symbols to
   the right MCSection, the asmprinters should just emit to the
   right section.
3. Since all zerofill stuff goes through mcstreamer anymore,
   MAI can have a bool "haszerofill" instead of having the textual
   directive to emit.

llvm-svn: 93838

Fix r93758. Use isel patterns instead of c++ selection code to select rbit and make sure we pick different instructions for ARM vs. Thumb2.

llvm-svn: 93829

llvm-svn: 93818

comments (fast isel, X86).  This doesn't seem
to break any functionality, but will introduce
cases where -g affects the generated code.  I'll
be fixing that.

llvm-svn: 93811

llvm-svn: 93797