| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
llvm-svn: 146457
|
|
|
|
| |
llvm-svn: 146456
|
|
|
|
| |
llvm-svn: 146455
|
|
|
|
| |
llvm-svn: 146454
|
|
|
|
| |
llvm-svn: 146453
|
|
|
|
| |
llvm-svn: 146451
|
|
|
|
| |
llvm-svn: 146448
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Necessary to parse Microsoft ATL code.
Example:
int array[] = {
0,
__if_exists(CLASS::Type) {2, }
3
};
will declare an array of 2 or 3 elements depending on if CLASS::Type exists or not.
llvm-svn: 146447
|
|
|
|
| |
llvm-svn: 146446
|
|
|
|
| |
llvm-svn: 146445
|
|
|
|
|
|
| |
inside a struct/union.
llvm-svn: 146444
|
|
|
|
|
|
| |
class has a base whose alignment will break the class layout. <rdar://problem/10551376>.
llvm-svn: 146443
|
|
|
|
| |
llvm-svn: 146442
|
|
|
|
| |
llvm-svn: 146441
|
|
|
|
| |
llvm-svn: 146440
|
|
|
|
|
|
| |
then read the file back in to verify use-list serialization/deserialization.
llvm-svn: 146439
|
|
|
|
|
|
|
|
| |
This should always be done as a matter of principal. I don't have a
case that exposes the problem. I just noticed this recently while
scanning the code and realized I meant to fix it long ago.
llvm-svn: 146438
|
|
|
|
|
|
| |
autodiscovery.
llvm-svn: 146437
|
|
|
|
|
|
|
|
|
|
|
| |
subdirectories to traverse into.
- Originally I wanted to avoid this and just autoscan, but this has one key
flaw in that new subdirectories can not automatically trigger a rerun of the
llvm-build tool. This is particularly a pain when switching back and forth
between trees where one has added a subdirectory, as the dependencies will
tend to be wrong. This will also eliminates FIXME implicitly.
llvm-svn: 146436
|
|
|
|
|
|
| |
components, it is generated.
llvm-svn: 146435
|
|
|
|
|
|
| |
--write-llvmbuild.
llvm-svn: 146434
|
|
|
|
| |
llvm-svn: 146433
|
|
|
|
|
|
| |
-relocation-model=static.
llvm-svn: 146432
|
|
|
|
| |
llvm-svn: 146431
|
|
|
|
|
|
| |
The motivation here is a "clever" implementation of strncmp(), which peels the first few comparisons via chained conditional expressions which ensure that the input arrays are known at compile time to be sufficiently large.
llvm-svn: 146430
|
|
|
|
| |
llvm-svn: 146429
|
|
|
|
|
|
|
|
| |
If we create new intervals for a variable that is being spilled, then those new intervals are not guaranteed to also spill. This means that anything reading from the original spilling value might not get the correct value if spills were missed.
Fixes <rdar://problem/10546864>
llvm-svn: 146428
|
|
|
|
|
|
|
|
|
|
| |
been passing for a while
with the recent clang compilers.
The latest I tried is: Apple clang version 3.1 (tags/Apple/clang-318.0.9) (based on LLVM 3.1svn)
llvm-svn: 146427
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There were two problems associated with this radar:
1. "settings show target.source-map" failed to show the source-map after, for example,
"settings set target.source-map /Volumes/data/lldb/svn/trunk/test/source-manager /Volumes/data/lldb/svn/trunk/test/source-manager/hidden"
has been executed to set the source-map.
2. "list -n main" failed to display the source of the main() function after we properly set the source-map.
The first was fixed by adding the missing functionality to TargetInstanceSettings::GetInstanceSettingsValue (Target.cpp)
and updating the support files PathMappingList.h/.cpp; the second by modifying SourceManager.cpp to fix several places
with incorrect logic.
Also added a test case test_move_and_then_display_source() to TestSourceManager.py, which moves main.c to hidden/main.c,
sets target.source-map to perform the directory mapping, and then verifies that "list -n main" can still show the main()
function.
llvm-svn: 146422
|
|
|
|
| |
llvm-svn: 146420
|
|
|
|
|
|
| |
it is not required.
llvm-svn: 146418
|
|
|
|
|
|
|
|
|
| |
These modifiers simply select either the low or high D subregister of a Neon
Q register. I've also removed the unimplemented 'p' modifier, which turns out
to be a bit different than the comment here suggests and as far as I can tell
was only intended for internal use in Apple's version of gcc.
llvm-svn: 146417
|
|
|
|
|
|
|
| |
fields by just following what comment says.
// rdar://10513599
llvm-svn: 146414
|
|
|
|
| |
llvm-svn: 146413
|
|
|
|
| |
llvm-svn: 146412
|
|
|
|
| |
llvm-svn: 146411
|
|
|
|
| |
llvm-svn: 146409
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
detected in the forward-CFG DFS. This prevents the reverse-CFG from
visiting blocks inside loops after blocks that dominate them in the
case where loops have multiple exits.
No testcase, because this fixes a bug which in practice only shows
up in a full optimizer run, due to the use-list order.
This fixes rdar://10422791 and others.
llvm-svn: 146408
|
|
|
|
| |
llvm-svn: 146407
|
|
|
|
|
|
| |
conversions in constant expressions.
llvm-svn: 146406
|
|
|
|
|
|
|
| |
This computes the offset of the layout sucessor block, considering its
alignment as well.
llvm-svn: 146401
|
|
|
|
| |
llvm-svn: 146400
|
|
|
|
|
|
| |
the subdirectories to find headers in submodules.
llvm-svn: 146398
|
|
|
|
| |
llvm-svn: 146397
|
|
|
|
| |
llvm-svn: 146396
|
|
|
|
| |
llvm-svn: 146395
|
|
|
|
|
|
|
|
|
| |
We will return a valid range when possible and omit the "permissions" key
when the memory is not readable, writeable or executeable. This will help us
know the difference between an error back from this packet and unsupported,
from just "this address isn't in a valid region".
llvm-svn: 146394
|
|
|
|
|
|
|
| |
actually a terribly good heuristic, and the world is too horrible for
it to work.
llvm-svn: 146393
|
|
|
|
| |
llvm-svn: 146392
|
|
|
|
|
|
|
|
|
| |
Downgrade the alignment of the initial constant island when constant
pool entries are moved elsewhere.
This is all gated by -arm-align-constant-islands.
llvm-svn: 146391
|