deleting the escape analysis pass.

llvm-svn: 63197

The memory alignment requirement on some of the mov{h|l}p{d|s} patterns are 16-byte. That is overly strict. These instructions read / write f64 memory locations without alignment requirement.

llvm-svn: 63195

llvm-svn: 63194

llvm-svn: 63193

llvm-svn: 63174

llvm-svn: 63173

Adds new option properties 'multi_val', 'one_or_more' and 'zero_or_one'.

llvm-svn: 63172

llvm-svn: 63171

llvm-svn: 63170

shift amounts, to avoid implicitly assuming that
target architectures will ignore the high bits.

llvm-svn: 63169

llvm-svn: 63164

llvm-svn: 63161

anyone will pay attention.

llvm-svn: 63155

llvm-svn: 63154

llvm-svn: 63152

llvm-svn: 63151

llvm-svn: 63149

mergeable string section. I don't see any bad impact of such decision
(rather then placing it into mergeable const section, as it was before),
but at least Darwin linker won't complain anymore.

The problem in LLVM is that we don't have special type for string constants
(like gcc does). Even more, we have two separate types: ConstatArray for non-null
strings and ConstantAggregateZero for null stuff.... It's a bit weird :)

llvm-svn: 63142

llvm-svn: 63139

llvm-svn: 63138

llvm-svn: 63136

llvm-svn: 63132

a uint64_t to verify that the value is in range for the given type,
to help catch accidental overflow. Fix a few places that relied on
getConstant implicitly truncating the value.

llvm-svn: 63128

llvm-svn: 63121

llvm-svn: 63120

llvm-svn: 63119

instead of via a by-reference argument. No functionality change.

llvm-svn: 63118

causing assertion failures in getSExtValue().
Fix it by making highWordBits actually contain what its name says,
and add some more unit-tests for APInt.
This fixes PR3419.

llvm-svn: 63107

llvm-svn: 63104

llvm-svn: 63091

llvm-svn: 63090

llvm-svn: 63089

llvm-svn: 63088

to help verify that the feature may be disabled through
the -mno-red-zone option.

llvm-svn: 63079

llvm-svn: 63078

Assorted debug info fixes.
- DW_AT_bit_size is only suitable for bitfields.
- Encode source location info for derived types.
- Source location and type size info is not useful for subroutine_type (info is included in respective DISubprogram) and array_type.

llvm-svn: 63077

llvm-svn: 63075

Don't use the Red Zone when dynamic stack realignment is needed.
This could be implemented, but most x86-64 ABIs don't require
dynamic stack realignment so it isn't urgent.

llvm-svn: 63074

llvm-svn: 63070

llvm-svn: 63067