- Jan 28, 2009
-
-
Dan Gohman authored
llvm-svn: 63170
-
Dan Gohman authored
shift amounts, to avoid implicitly assuming that target architectures will ignore the high bits. llvm-svn: 63169
-
Bill Wendling authored
llvm-svn: 63164
-
Evan Cheng authored
llvm-svn: 63161
-
Dale Johannesen authored
anyone will pay attention. llvm-svn: 63155
-
Devang Patel authored
llvm-svn: 63154
-
Dale Johannesen authored
llvm-svn: 63152
-
Dale Johannesen authored
llvm-svn: 63151
-
Bill Wendling authored
llvm-svn: 63149
-
- Jan 27, 2009
-
-
Anton Korobeynikov authored
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
-
Dan Gohman authored
llvm-svn: 63139
-
Dale Johannesen authored
llvm-svn: 63138
-
Dale Johannesen authored
llvm-svn: 63136
-
Evan Cheng authored
llvm-svn: 63132
-
Dan Gohman authored
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
-
Dan Gohman authored
llvm-svn: 63121
-
Dan Gohman authored
llvm-svn: 63120
-
Dan Gohman authored
llvm-svn: 63119
-
Dan Gohman authored
instead of via a by-reference argument. No functionality change. llvm-svn: 63118
-
Torok Edwin authored
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
-
Dan Gohman authored
llvm-svn: 63104
-
Owen Anderson authored
llvm-svn: 63091
-
Evan Cheng authored
llvm-svn: 63090
-
Evan Cheng authored
llvm-svn: 63089
-
Dan Gohman authored
llvm-svn: 63088
-
Dan Gohman authored
to help verify that the feature may be disabled through the -mno-red-zone option. llvm-svn: 63079
-
Dan Gohman authored
llvm-svn: 63078
-
Devang Patel authored
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
-
Dan Gohman authored
llvm-svn: 63075
-
Dan Gohman authored
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
-
Evan Cheng authored
llvm-svn: 63070
-
Dale Johannesen authored
llvm-svn: 63067
-
- Jan 26, 2009
-
-
Scott Michel authored
- Update DWARF debugging support. llvm-svn: 63059
-
Scott Michel authored
doesn't support it. The default is set to 'true', so this should not impact any other target backends. llvm-svn: 63058
-
Dan Gohman authored
disabled by default; I'll enable it when I hook it up with the llvm-gcc flag which controls it. llvm-svn: 63056
-
Steve Naroff authored
llvm-svn: 63050
-
Owen Anderson authored
llvm-svn: 63049
-
Duncan Sands authored
checking logic. Rather than make the checking more complicated, I've tweaked some logic to make things conform to how the checking thought things ought to be, since this results in a simpler "mental model". llvm-svn: 63048
-
Ted Kremenek authored
llvm-svn: 63044
-
Dan Gohman authored
llvm-svn: 63042
-