| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
llvm-svn: 66223
|
| |
|
|
| |
llvm-svn: 66001
|
| |
|
|
| |
llvm-svn: 66000
|
| |
|
|
|
|
| |
per Chris' suggestion. Slightly faster.
llvm-svn: 65999
|
| |
|
|
|
|
| |
caused them to be considered trivially dead. Fix this.
llvm-svn: 65979
|
| |
|
|
|
|
|
| |
feed into llvm.dbg.declare nodes, as well as
the debug directives themselves.
llvm-svn: 65976
|
| |
|
|
|
|
|
|
| |
use, check also for the case where it has two uses,
the other being a llvm.dbg.declare. This is needed so
debug info doesn't affect codegen.
llvm-svn: 65970
|
| |
|
|
| |
llvm-svn: 65961
|
| |
|
|
| |
llvm-svn: 65960
|
| |
|
|
|
|
| |
and put @file directives on their own comment line.
llvm-svn: 65920
|
| |
|
|
|
|
|
|
| |
info with it.
Don't count debug info insns against the scan maximum
in FindAvailableLoadedValue (lest they affect codegen).
llvm-svn: 65910
|
| |
|
|
| |
llvm-svn: 65620
|
| |
|
|
|
|
| |
conditional branch predecessors.
llvm-svn: 65509
|
| |
|
|
| |
llvm-svn: 65456
|
| |
|
|
|
|
|
|
|
|
|
| |
predecessor, instead of removing it. This fixes following tests from llvmgcc42 testsuite.
gcc.c-torture/execute/20000605-3.c
gcc.c-torture/execute/20020619-1.c
gcc.c-torture/execute/20030920-1.c
gcc.c-torture/execute/loop-ivopts-1.c
llvm-svn: 65353
|
| |
|
|
|
|
| |
inline-threshold option is used by the inliner.
llvm-svn: 65309
|
| |
|
|
| |
llvm-svn: 65228
|
| |
|
|
|
|
| |
other passes, e.g. loop strength reduction.
llvm-svn: 65134
|
| |
|
|
|
|
| |
Will re-think about this according to Chris's comments.
llvm-svn: 65126
|
| |
|
|
|
|
|
|
| |
Currently this pass will delete the variable declaration info,
and keep the line number info. But the kept line number info is not updated,
and some is redundant or not correct, this patch just updates those info.
llvm-svn: 65123
|
| |
|
|
| |
llvm-svn: 64626
|
| |
|
|
|
|
|
| |
calls with the tail marker when inlining them through an invoke. Patch,
testcase, and perfect analysis by Jay Foad!
llvm-svn: 64364
|
| |
|
|
|
|
| |
llvm.dbg.func.start also.
llvm-svn: 64278
|
| |
|
|
| |
llvm-svn: 64242
|
| |
|
|
|
|
| |
during inlining.
llvm-svn: 64209
|
| |
|
|
| |
llvm-svn: 64207
|
| |
|
|
| |
llvm-svn: 63888
|
| |
|
|
| |
llvm-svn: 63876
|
| |
|
|
| |
llvm-svn: 63802
|
| |
|
|
| |
llvm-svn: 63781
|
| |
|
|
| |
llvm-svn: 63700
|
| |
|
|
|
|
| |
the branch block.
llvm-svn: 63687
|
| |
|
|
| |
llvm-svn: 63671
|
| |
|
|
| |
llvm-svn: 63618
|
| |
|
|
| |
llvm-svn: 63600
|
| |
|
|
| |
llvm-svn: 63402
|
| |
|
|
| |
llvm-svn: 63198
|
| |
|
|
|
|
|
| |
more accurate change loses more than it gains on
benchmarks.
llvm-svn: 62938
|
| |
|
|
|
|
| |
Little practical effect.
llvm-svn: 62908
|
| |
|
|
|
|
|
|
|
| |
There is now a direct way from value-use-iterator to incoming block in PHINode's API.
This way we avoid the iterator->index->iterator trip, and especially the costly
getOperandNo() invocation. Additionally there is now an assertion that the iterator
really refers to one of the PHI's Uses.
llvm-svn: 62869
|
| |
|
|
| |
llvm-svn: 62561
|
| |
|
|
| |
llvm-svn: 62546
|
| |
|
|
|
|
| |
trapping instruction be executed unconditionally.
llvm-svn: 62541
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
llvm-gcc. Most likely, it's miscompiling one of the "gen*" programs:
/Volumes/Sandbox/Buildbot/llvm/full-llvm/build/llvm-gcc.obj/./prev-gcc/xgcc -B/Volumes/Sandbox/Buildbot/llvm/full-llvm/build/llvm-gcc.obj/./prev-gcc/ -B/Volumes/Sandbox/Buildbot/llvm/full-llvm/build/llvm-gcc.install/i386-apple-darwin9.6.0/bin/ -c -g -O2 -mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -mdynamic-no-pic -DHAVE_CONFIG_H -DGENERATOR_FILE -I. -Ibuild -I../../llvm-gcc.src/gcc -I../../llvm-gcc.src/gcc/build -I../../llvm-gcc.src/gcc/../include -I./../intl -I../../llvm-gcc.src/gcc/../libcpp/include -I../../llvm-gcc.src/gcc/../libdecnumber -I../libdecnumber -I/Volumes/Sandbox/Buildbot/llvm/full-llvm/build/llvm.obj/include -I/Volumes/Sandbox/Buildbot/llvm/full-llvm/build/llvm.src/include -DENABLE_LLVM -I/Volumes/Sandbox/Buildbot/llvm/full-llvm/build/llvm.obj/../llvm.src/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -o build/gencondmd.o build/gencondmd.c
../../llvm-gcc.src/gcc/config/i386/mmx.md:926: error: expected '}' before ')' token
../../llvm-gcc.src/gcc/config/i386/mmx.md:926: warning: excess elements in struct initializer
../../llvm-gcc.src/gcc/config/i386/mmx.md:926: warning: (near initialization for 'insn_conditions[4]')
../../llvm-gcc.src/gcc/config/i386/mmx.md:926: error: expected '}' before ')' token
../../llvm-gcc.src/gcc/config/i386/mmx.md:926: error: expected ',' or ';' before ')' token
../../llvm-gcc.src/gcc/config/i386/mmx.md:927: error: expected identifier or '(' before ',' token
../../llvm-gcc.src/gcc/config/i386/sse.md:3458: error: expected identifier or '(' before ',' token
...
llvm-svn: 62506
|
| |
|
|
|
|
|
|
|
| |
we assumed a CFG structure that would be valid when all code in
the function is reachable, but not all code is necessarily
reachable. Do a simple, but horrible, CFG walk to check for this
case.
llvm-svn: 62487
|
| |
|
|
| |
llvm-svn: 62477
|
| |
|
|
|
|
|
|
|
|
| |
because of dead code, a phi could use the speculated instruction
that was not in "BB2". Make this check explicit and tighten up
some other corners. This fixes PR3292. No testcase becauase this
depends entirely on visitation order of blocks and requires a
sequence of 8 passes to repro.
llvm-svn: 62476
|
| |
|
|
|
|
| |
check. No functionality change.
llvm-svn: 62474
|
| |
|
|
| |
llvm-svn: 62384
|
| |
|
|
| |
llvm-svn: 62377
|