of cmake.

llvm-svn: 78768

evaluation.

llvm-svn: 78692

llvm-svn: 78690

llvm-svn: 78660

llvm-svn: 78641

llvm-svn: 78640

yet (I'm not even sure what they do).

llvm-svn: 78639

(and outputting a diagnostic pointing at the wrong place), all of which lead to
much confusion.

llvm-svn: 78637

and short. Well, it's kinda short. Definitely nasty and brutish.

The front-end generates the register/unregister calls into the SjLj runtime,
call-site indices and landing pad dispatch. The back end fills in the LSDA
with the call-site information provided by the front end. Catch blocks are
not yet implemented.

Built on Darwin and verified no llvm-core "make check" regressions.

llvm-svn: 78625

llvm-svn: 78576

llvm-svn: 78575

llvm-svn: 78571

instead of syntactically as a string.  This means that it keeps track of the 
segment, section, flags, etc directly and asmprints them in the right format.
This also includes parsing and validation support for llvm-mc and 
"attribute(section)", so we should now start getting errors about invalid 
section attributes from the compiler instead of the assembler on darwin.

Still todo: 
1) Uniquing of darwin mcsections
2) Move all the Darwin stuff out to MCSectionMachO.[cpp|h]
3) there are a few FIXMEs, for example what is the syntax to get the
   S_GB_ZEROFILL segment type?

llvm-svn: 78547

This totally optimizes PIC16 sections by not having an 'isdirective' bit anymore!! ;-)

llvm-svn: 78517

llvm-mc's purpose yet and we'll want to switch to creating semantic sections
at some point.

llvm-svn: 78509

 - Part of optimal static profiling patch sequence by Andreas Neustifter.

llvm-svn: 78485

 - Part of optimal static profiling patch sequence by Andreas Neustifter.

 - Store edge, block, and function information separately for each functions
   (instead of in one giant map).

 - Return frequencies as double instead of int, and use a sentinel value for
   missing information.

llvm-svn: 78477

llvm-svn: 78463

I can clean this up a bit more and do way with the TheCondState and just use
the top element on the TheCondStack if not empty.  Also may tweak the code
around ParseConditionalAssemblyDirectives() to simplify the AsmParser code.

llvm-svn: 78423

llvm-svn: 78405

llvm-svn: 78282

Privatize the StructType table, which unfortunately involves routing contexts through a number of APIs.

llvm-svn: 78258

 - Part of optimal static profiling patch sequence by Andreas Neustifter.

llvm-svn: 78247

for use with sys::Path::GetMainExecutable, to avoid warnings
with -pedantic.

llvm-svn: 78245

just argv[0]. And remove the code for searching the current
working directory and for searching PATH; the point of FindExecutable
is not to find whatever version of the executable can be found by
searching around, but to find an executable that accompanies the
current executable.

Update the tools to use sys::Program::FindProgramByName when they
want PATH searching.

llvm-svn: 78240

 - Part of optimal static profiling patch sequence by Andreas Neustifter.

llvm-svn: 78199

llvm-svn: 78184

Patch by Sandeep Patel

llvm-svn: 78183

llvm-svn: 78133

Factor some of the constants+context related code out into a separate header, to make LLVMContextImpl.h
not hideous.  Also, fix some MSVC compile errors.

llvm-svn: 78115

llvm-svn: 78047

llvm-svn: 77973

llvm-svn: 77960

llvm-svn: 77950

This is not just a matter of passing in the target triple from the module;
currently backends are making decisions based on the build and host
architecture. The goal is to migrate to making these decisions based off of the
triple (in conjunction with the feature string). Thus most clients pass in the
target triple, or the host triple if that is empty.

This has one important change in the way behavior of the JIT and llc.

For the JIT, it was previously selecting the Target based on the host
(naturally), but it was setting the target machine features based on the triple
from the module. Now it is setting the target machine features based on the
triple of the host.

For LLC, -march was previously only used to select the target, the target
machine features were initialized from the module's triple (which may have been
empty). Now the target triple is taken from the module, or the host's triple is
used if that is empty. Then the triple is adjusted to match -march.

The take away is that -march for llc is now used in conjunction with the host
triple to initialize the subtarget. If users want more deterministic behavior
from llc, they should use -mtriple, or set the triple in the input module.

llvm-svn: 77946

llvm-svn: 77835

llvm-svn: 77804

llvm-svn: 77787

llvm-svn: 77761

 - Uses MCAsmToken::getIdentifier which returns the (sub)string representing the
   meaningfull contents a string or identifier token.

 - Directives aren't done yet.

llvm-svn: 77739