| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Because of win32 mangling, we produce symbol and section names with
funny characters in them, most notably @ characters.
MC would choke on trying to parse its own assembly output. This patch addresses
that by:
- Making @ trigger quoting of symbol names
- Also quote section names in the same way
- Just parse section names like other identifiers (to allow for quotes)
- Don't assume @ signifies a symbol variant if it is in a string.
Differential Revision: http://llvm-reviews.chandlerc.com/D1945
llvm-svn: 192758
|
| |
|
|
|
|
|
|
| |
No functionality change, but exposes the API so that codegen can use it too.
Patch by Katya Romanova.
llvm-svn: 192757
|
| |
|
|
| |
llvm-svn: 192756
|
| |
|
|
| |
llvm-svn: 192755
|
| |
|
|
| |
llvm-svn: 192754
|
| |
|
|
|
|
| |
Patch by Yaron Keren
llvm-svn: 192753
|
| |
|
|
| |
llvm-svn: 192752
|
| |
|
|
| |
llvm-svn: 192751
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This changes the SelectionDAG scheduling preference to source
order. Soon, the SelectionDAG scheduler can be bypassed saving
a nice chunk of compile time.
Performance differences that result from this change are often a
consequence of register coalescing. The register coalescer is far from
perfect. Bugs can be filed for deficiencies.
On x86 SandyBridge/Haswell, the source order schedule is often
preserved, particularly for small blocks.
Register pressure is generally improved over the SD scheduler's ILP
mode. However, we are still able to handle large blocks that require
latency hiding, unlike the SD scheduler's BURR mode. MI scheduler also
attempts to discover the critical path in single-block loops and
adjust heuristics accordingly.
The MI scheduler relies on the new machine model. This is currently
unimplemented for AVX, so we may not be generating the best code yet.
Unit tests are updated so they don't depend on SD scheduling heuristics.
llvm-svn: 192750
|
| |
|
|
|
|
|
|
| |
twice and just look up the value. Fix the one case where
we were trying to create a subprogram DIE and we should already
have had one. Reflow formatting in collectDeadVariables while fixing.
llvm-svn: 192749
|
| |
|
|
|
|
|
| |
and remove a call to getNonCompileUnitScope as a method
shouldn't be in the compile unit scope.
llvm-svn: 192748
|
| |
|
|
| |
llvm-svn: 192747
|
| |
|
|
| |
llvm-svn: 192743
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some background: One can pass compiled resource files (.res files) directly
to the linker on Windows. If a resource file is given, the linker will run
"cvtres" command in background to convert the resource file to a COFF file
to link it.
What I'm trying to do with this patch is to make the linker to recognize
the resource file by file magic, so that it can run cvtres command.
Differential Revision: http://llvm-reviews.chandlerc.com/D1943
llvm-svn: 192742
|
| |
|
|
| |
llvm-svn: 192737
|
| |
|
|
|
|
| |
scalar signed saturating negate instructions.
llvm-svn: 192733
|
| |
|
|
| |
llvm-svn: 192732
|
| |
|
|
| |
llvm-svn: 192731
|
| |
|
|
|
|
| |
PR17309
llvm-svn: 192730
|
| |
|
|
|
|
|
|
|
|
| |
- Type of index used in extract_vector_elt or insert_vector_elt supposes
to be TLI.getVectorIdxTy() which is pointer type on most targets. It'd
better to truncate (or zero-extend in case it's changed later) it to
mask element type to guarantee they are matching instead of asserting
that.
llvm-svn: 192722
|
| |
|
|
|
|
|
|
|
|
| |
- Lower signed division by constant powers-of-2 to target-independent
DAG operators instead of target-dependent ones to support them better
on targets where vector types are legal but shift operators on that
types are illegal. E.g., on AVX, PSRAW is only available on <8 x i16>
though <16 x i16> is a legal type.
llvm-svn: 192721
|
| |
|
|
| |
llvm-svn: 192717
|
| |
|
|
|
|
| |
defined.
llvm-svn: 192709
|
| |
|
|
|
|
| |
MachineInstr::addOperand().
llvm-svn: 192707
|
| |
|
|
| |
llvm-svn: 192699
|
| |
|
|
|
|
| |
(atleast) windows and darwin.
llvm-svn: 192697
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
llvm-c headers.
This new library will be linked in when using the "all-targets"
component and contains the LLVMInitializeAll* functions.
This means that those functions will exist as real symbols in
the shared library, and can therefore can be called from
bindings that are using ffi the shared library.
llvm-svn: 192690
|
| |
|
|
| |
llvm-svn: 192681
|
| |
|
|
| |
llvm-svn: 192678
|
| |
|
|
|
|
| |
x86_sse42_crc32_32_8 and was not mapped to a clang builtin. I'm not even sure why this form of the instruction is even called out explicitly in the docs. Also add AutoUpgrade support to convert it into the other intrinsic with appropriate trunc and zext.
llvm-svn: 192672
|
| |
|
|
|
|
|
|
|
| |
rdar:15221834 False AVX register dependencies cause 5x slowdown on
flops-5/6 and significant slowdown on several others.
This was blocking the switch to MI-Sched.
llvm-svn: 192669
|
| |
|
|
|
|
| |
parts of the accumulators and gets expanded post-RA.
llvm-svn: 192667
|
| |
|
|
|
|
| |
of relying on AddedComplexity.
llvm-svn: 192665
|
| |
|
|
| |
llvm-svn: 192663
|
| |
|
|
| |
llvm-svn: 192662
|
| |
|
|
| |
llvm-svn: 192661
|
| |
|
|
| |
llvm-svn: 192660
|
| |
|
|
|
|
|
|
| |
externally_initialized.
Thanks to Shuxin Yang for catching this.
llvm-svn: 192637
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
through bitcast, ptrtoint, and inttoptr instructions. This is valid
only if the related instructions are in that same basic block, otherwise
we may reference variables that were not live accross basic blocks
resulting in undefined virtual registers.
The bug was exposed when both SDISel and FastISel were used within the same
function, i.e., one basic block is issued with FastISel and another with SDISel,
as demonstrated with the testcase.
<rdar://problem/15192473>
llvm-svn: 192636
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This pass is needed to break false dependencies. Without it, unlucky
register assignment can result in wild (5x) swings in
performance. This pass was trying to handle AVX but not getting it
right. AVX doesn't have partial register defs, it has unused register
reads in which the high bits of a source operand are copied into the
unused bits of the dest.
Fixing this requires conservative liveness analysis. This is awkard
because the pass already has its own pseudo-liveness. However, proper
liveness is expensive, and we would like to use a generic utility to
compute it. The fix only invokes liveness on-demand. It is rare to
detect a case that needs undef-read dependence breaking, but when it
happens, it can be needed many times within a very large block.
I think the existing heuristic which uses a register window of 16 is
too conservative for loop-carried false dependencies. If the loop is a
reduction. The out-of-order engine may be able to execute several loop
iterations in parallel. However, I'll leave this tuning exercise for
next time.
llvm-svn: 192635
|
| |
|
|
| |
llvm-svn: 192634
|
| |
|
|
| |
llvm-svn: 192633
|
| |
|
|
|
|
|
|
|
|
|
|
| |
a) x86-64 TLS has been documented
b) the code path should use movq for the correct relocation
to be generated.
I've also added a fixme for the test case that we should improve
the code generated, it should look something like is documented
in the tls abi document.
llvm-svn: 192631
|
| |
|
|
| |
llvm-svn: 192630
|
| |
|
|
| |
llvm-svn: 192629
|
| |
|
|
|
|
|
|
|
| |
Clobbering is exclusive not inclusive on register units.
For liveness, we need to consider all the preserved registers.
e.g. A regmask that clobbers YMM0 may preserve XMM0.
Units are only clobbered when all super-registers are clobbered.
llvm-svn: 192623
|
| |
|
|
|
|
|
|
|
|
| |
Some clients may add block live ins and may track liveness over a
large scope. This guarantees an efficient implementation in all cases
with no memory allocation/deallocation, independent of the number of
target registers. It could be slightly less convenient but is fine in
the expected case.
llvm-svn: 192622
|
| |
|
|
| |
llvm-svn: 192621
|
| |
|
|
| |
llvm-svn: 192619
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Clean up creation of static member DIEs. We can create static member DIEs from
two places, so we call getOrCreateStaticMemberDIE from the two places.
getOrCreateStaticMemberDIE will get or create the context DIE first, then it
will check if the DIE already exists, if not, we create the static member DIE
and add it to the context.
Creation of static member DIEs are handled in a similar way as subprogram DIEs.
llvm-svn: 192618
|