| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
discovered a miscompilation in it, and it's not easily
fixable at the optimizer level. I'll investigate reimplementing it in DAGCombine.
llvm-svn: 112575
|
| |
|
|
| |
llvm-svn: 112571
|
| |
|
|
|
|
| |
handling of those nodes when seeking for scalars inside vector shuffles
llvm-svn: 112570
|
| |
|
|
|
|
| |
Goodnow II!
llvm-svn: 112569
|
| |
|
|
| |
llvm-svn: 112568
|
| |
|
|
|
|
|
|
|
|
| |
Eventually, we want to disable physreg coalescing completely, and let the
register allocator do its job using hints.
This option makes it possible to measure the impact of disabling physreg
coalescing.
llvm-svn: 112567
|
| |
|
|
| |
llvm-svn: 112566
|
| |
|
|
|
|
| |
testcase for inline namespace fun.
llvm-svn: 112565
|
| |
|
|
| |
llvm-svn: 112564
|
| |
|
|
|
|
| |
semantics slightly. No functionality change in the absence of inline namespaces. Also, change a few places where inline namespaces actually make a difference to be prepared for them.
llvm-svn: 112563
|
| |
|
|
|
|
| |
transparent contexts, and would be wrong to do so with inline namespaces.
llvm-svn: 112562
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
instantiating the parameters. In a perfect world, this wouldn't
matter, and compilers are free to instantiate in any order they
want. However, every other compiler seems to instantiate the return
type first, and some code (in this case, Boost.Polygon) depends on
this and SFINAE to avoid instantiating something that shouldn't be
instantiated.
We could fight this battle, and insist that Clang is allowed to do
what it does, but it's not beneficial: it's more predictable to
instantiate this way, in source order. When we implement
late-specified return types, we'll need to instantiate the return type
last when it was late-specified, hence the FIXME.
We now compile Boost.Polygon properly.
llvm-svn: 112561
|
| |
|
|
| |
llvm-svn: 112560
|
| |
|
|
|
|
| |
things we can't handle.
llvm-svn: 112559
|
| |
|
|
| |
llvm-svn: 112558
|
| |
|
|
|
|
| |
with the descriptions of Mod and Ref.
llvm-svn: 112557
|
| |
|
|
|
|
|
| |
process being debugged in the TestBase.tearDown() instead of letting it continue
and finish.
llvm-svn: 112556
|
| |
|
|
| |
llvm-svn: 112555
|
| |
|
|
| |
llvm-svn: 112554
|
| |
|
|
| |
llvm-svn: 112553
|
| |
|
|
| |
llvm-svn: 112552
|
| |
|
|
|
|
|
|
|
|
|
|
| |
of that parameter, reduce the level by the number of active template
argument lists rather than by 1. The number of active template
argument lists is only > 1 when we have a class template partial
specialization of a member template of a class template that itself is
a member template of another class template.
... and Boost.MSM does this. Fixes PR7669.
llvm-svn: 112551
|
| |
|
|
|
|
|
|
| |
constant folding methods. Additionally,
use the ConstantExpr::get*() methods to simplify some constant folding.
llvm-svn: 112550
|
| |
|
|
| |
llvm-svn: 112549
|
| |
|
|
|
|
| |
parameter.
llvm-svn: 112548
|
| |
|
|
|
|
| |
of os command to lldbtest.TestBase.system() method.
llvm-svn: 112547
|
| |
|
|
|
|
|
| |
scheduling opportunities (extra instruction can go in between
MOVT / MOVW pair removing the stall).
llvm-svn: 112546
|
| |
|
|
| |
llvm-svn: 112545
|
| |
|
|
| |
llvm-svn: 112543
|
| |
|
|
|
|
| |
them from test cases instead of issuing "make clean; make ..." os command.
llvm-svn: 112542
|
| |
|
|
| |
llvm-svn: 112541
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
persistent variables were staying around too long.
This caused the following problem:
- A persistent result variable is created for the
result of an expression. The pointer to the
corresponding Decl is stored in the variable.
- The persistent variable is looked up during
struct generation (correctly) using its Decl.
- Another expression defines a new result variable
which happens to have a Decl in the same place
as the original result variable.
- The persistent variable is looked up during
struct generation using its Decl, but the old
result variable appears first in the list and
has the same Decl pointer.
The fix is to destroy parser-specific data when
it is no longer valid.
Also improved some logging as I diagnosed the
bug.
llvm-svn: 112540
|
| |
|
|
|
|
|
|
| |
results from ComputeValueKnownInPredecessors
(indicating undef), and re-use existing constant folding APIs.
llvm-svn: 112539
|
| |
|
|
|
|
|
| |
is meant to do exactly the same thing. Thanks to Jim Grosbach for pointing this
out! :-)
llvm-svn: 112538
|
| |
|
|
| |
llvm-svn: 112537
|
| |
|
|
|
|
| |
is launched with the -e option on Mac OS X.
llvm-svn: 112536
|
| |
|
|
| |
llvm-svn: 112535
|
| |
|
|
|
|
|
|
|
|
|
| |
kill flag.
This could cause duplicate kill flags when the same register was used twice in a
continuous sequence of STRs.
There is no small test case. <rdar://problem/8218046>
llvm-svn: 112534
|
| |
|
|
| |
llvm-svn: 112533
|
| |
|
|
| |
llvm-svn: 112532
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
taken from Python 2.7's subprocess.check_output() convenience function. The
purpose of this method is to run the os command with arguments and return its
output as a byte string.
Modified hello_world/TestHelloWorld.py to have two test cases:
o test_with_dsym_and_run_command
o test_with_dwarf_and_process_launch_api
with the dsym case conditioned on sys.platform.startswith("darwin") being true.
The two cases utilize the system() method to invoke "make clean; make MAKE_DYSM=YES/NO"
to prepare for the appropriate debugging format before running the test logic.
llvm-svn: 112530
|
| |
|
|
| |
llvm-svn: 112529
|
| |
|
|
|
|
| |
is-function-local flag in metadata uniquing bits.
llvm-svn: 112528
|
| |
|
|
|
|
|
|
| |
storing pointers to objects inside a std::vector.
These objects can move around as the std::vector
changes, invalidating the pointers.
llvm-svn: 112527
|
| |
|
|
|
|
|
|
|
|
| |
namely when the friend function prototype is already used
at the point of the template definition that is supposed
to inject the friend function. Testcase verifies four
scenarios.
I would like receive some code review for this.
llvm-svn: 112524
|
| |
|
|
|
|
|
|
|
| |
deduction where the parameter is a function reference, function
pointer, or member function pointer and the argument is an overloaded
function. Fixes <rdar://problem/8360106>, a template argument
deduction issue found by Boost.Filesystem.
llvm-svn: 112523
|
| |
|
|
|
|
| |
Auto-upgrade the old intrinsic and update tests.
llvm-svn: 112507
|
| |
|
|
|
|
| |
intrinsic.
llvm-svn: 112504
|
| |
|
|
|
|
|
|
|
| |
address of locals is calculated, so this should
help relieve register pressure a bit. Recalculating the local address is
almost always going to be better than spilling.
llvm-svn: 112503
|
| |
|
|
|
|
|
|
| |
and you can turn this on with:
lldb -e
llvm-svn: 112502
|