diff options
| author | Bill Schmidt <wschmidt@linux.vnet.ibm.com> | 2013-06-13 20:23:34 +0000 |
|---|---|---|
| committer | Bill Schmidt <wschmidt@linux.vnet.ibm.com> | 2013-06-13 20:23:34 +0000 |
| commit | 11729224bf93d61ca6c31c02bfe4f1b171f8a4a7 (patch) | |
| tree | bfe1f8350798262d4f0df4a434b27aeabebde782 /tools/bugpoint | |
| parent | 2948e693cb9ed0f99e8ba2448459d8a34f091075 (diff) | |
| download | llvm-11729224bf93d61ca6c31c02bfe4f1b171f8a4a7.tar.gz llvm-11729224bf93d61ca6c31c02bfe4f1b171f8a4a7.tar.bz2 llvm-11729224bf93d61ca6c31c02bfe4f1b171f8a4a7.tar.xz | |
[PowerPC] Disable fast-isel for existing -O0 tests for PowerPC.
This is a preliminary patch for fast instruction selection on
PowerPC. Code generation can differ between DAG isel and fast isel.
Existing tests that specify -O0 were written to expect DAG isel. Make
this explicit by adding -fast-isel=false to the tests.
In some cases specifying -fast-isel=false produces different code even
when there isn't a fast instruction selector specified. This is
because TM.Options.EnableFastISel = 1 at -O0 whether or not a FastISel
object exists. Thus disabling fast isel can actually produce less
conservative code. Because of this, some of the expected code
generation in the -O0 tests needs to be adjusted.
In particular, handling of function arguments is less conservative
with -fast-isel=false (see isOnlyUsedInEntryBlock() in
SelectionDAGBuilder.cpp). This results in fewer stack accesses and,
in some cases, reduced stack size as uselessly loaded values are no
longer stored back to spill locations in the stack.
No functional change with this patch; test case adjustments only.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@183939 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'tools/bugpoint')
0 files changed, 0 insertions, 0 deletions