isn't legal.

llvm-svn: 81492

llvm-svn: 81484

how to fold notionally-out-of-bounds array getelementptr indices instead
of just doing these in lib/Analysis/ConstantFolding.cpp, because it can
be done in a fairly general way without TargetData, and because not all
constants are visited by lib/Analysis/ConstantFolding.cpp. This enables
more constant folding.

Also, set the "inbounds" flag when the getelementptr indices are
one-past-the-end.

llvm-svn: 81483

within the notional bounds of the static type of the getelementptr (which
is not the same as "inbounds") from GlobalOpt into a utility routine,
and use it in ConstantFold.cpp to check whether there are any mis-behaved
indices.

llvm-svn: 81478

llvm-svn: 81473

llvm-svn: 81468

llvm-svn: 81466

llvm-svn: 81465

post-decrement load/store.

llvm-svn: 81464

llvm-svn: 81463

that things like .word can be parsed as target specific.  Moved parsing .word
out of AsmParser.cpp into X86AsmParser.cpp as it is 2 bytes on X86 and 4 bytes
for other targets that support the .word directive.

llvm-svn: 81461

llvm-svn: 81459

various widths.

llvm-svn: 81458

including segment offsets and (for 8-bit operands)
absolute offsets.

llvm-svn: 81457

ones capable of accessing R/M operands instead of just
registers.

llvm-svn: 81456

llvm-svn: 81454

llvm-svn: 81452

llvm-svn: 81450

llvm-svn: 81449

llvm-svn: 81448

llvm-svn: 81447

llvm-svn: 81445

llvm-svn: 81443

llvm-svn: 81438

used by a terminator in another.

llvm-svn: 81437

llvm-svn: 81436

from the exception tables. However, Duncan explained why it's a can of worms to
do it the GCC way. I went back to doing it the LLVM way and added Duncan's
explanation so that I don't do this again in the future.

llvm-svn: 81434

llvm-svn: 81432

llvm-svn: 81427

llvm-svn: 81426

like what GCC outputs. The mysterious code to insert padding wasn't in GCC at
all. I modified the TType base offset code to calculate the offset like GCC
does, though.

llvm-svn: 81424

llvm-svn: 81422

code within it was the same inside and out. There's still a problem of the
TypeInfoSize should be the size of the TType format encoding (at least that's
what GCC thinks it should be).

llvm-svn: 81417

llvm-svn: 81416

llvm-svn: 81415

llvm-svn: 81409

sizeof(DW_EH_PE_udata4).

llvm-svn: 81408

llvm-svn: 81406

Basically, this patch is working towards removing the hard-coded values that are
output for the CIE. In particular, the CIE augmentation and the CIE augmentation
size. Both of these should be calculated. In the process, I was able to make a
bunch of code simpler.

The encodings for the personality, LSDA, and FDE in the CIE are still not
correct. They should be generated either from target-specific callbacks (blech!)
or grokked from first-principles.

llvm-svn: 81404

llvm-svn: 81403