| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
llvm-svn: 89863
|
| |
|
|
| |
llvm-svn: 89329
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Support mips1 like load/store of doubles:
Instead of:
sdc $f0, X($3)
Generate:
swc $f0, X($3)
swc $f1, X+4($3)
llvm-svn: 89322
|
| |
|
|
| |
llvm-svn: 88892
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add a smarter constant pool loading, instead of:
lui $2, %hi($CPI1_0)
addiu $2, $2, %lo($CPI1_0)
lwc1 $f0, 0($2)
Generate:
lui $2, %hi($CPI1_0)
lwc1 $f0, %lo($CPI1_0)($2)
llvm-svn: 88886
|
| |
|
|
| |
llvm-svn: 81293
|
| |
|
|
| |
llvm-svn: 79992
|
| |
|
|
|
|
|
| |
implemented somewhat differently than before, but it should have
the same functionality and the previous testcase passes again.
llvm-svn: 78900
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is not just a matter of passing in the target triple from the module;
currently backends are making decisions based on the build and host
architecture. The goal is to migrate to making these decisions based off of the
triple (in conjunction with the feature string). Thus most clients pass in the
target triple, or the host triple if that is empty.
This has one important change in the way behavior of the JIT and llc.
For the JIT, it was previously selecting the Target based on the host
(naturally), but it was setting the target machine features based on the triple
from the module. Now it is setting the target machine features based on the
triple of the host.
For LLC, -march was previously only used to select the target, the target
machine features were initialized from the module's triple (which may have been
empty). Now the target triple is taken from the module, or the host's triple is
used if that is empty. Then the triple is adjusted to match -march.
The take away is that -march for llc is now used in conjunction with the host
triple to initialize the subtarget. If users want more deterministic behavior
from llc, they should use -mtriple, or set the triple in the input module.
llvm-svn: 77946
|
| |
|
|
|
|
| |
a sad mistake that is regretted. :)
llvm-svn: 76935
|
| |
|
|
|
|
|
|
| |
on linux platforms. The binutils assembler does not
recognize the "s" flag, see for example
http://sourceware.org/binutils/docs/as/Section.html
llvm-svn: 76733
|
| |
|
|
|
|
| |
updating a mips testcase to expect it.
llvm-svn: 76707
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
integer and floating-point opcodes, introducing
FAdd, FSub, and FMul.
For now, the AsmParser, BitcodeReader, and IRBuilder all preserve
backwards compatability, and the Core LLVM APIs preserve backwards
compatibility for IR producers. Most front-ends won't need to change
immediately.
This implements the first step of the plan outlined here:
http://nondot.org/sabre/LLVMNotes/IntegerOverflow.txt
llvm-svn: 72897
|
| |
|
|
| |
llvm-svn: 72485
|
| |
|
|
| |
llvm-svn: 62279
|
| |
|
|
|
|
|
|
|
|
|
| |
scheduling dependencies. Add assertion checks to help catch
this.
It appears the Mips target defaults to list-td, and it has a
regression test that uses a physreg dependence. Such code was
liable to be miscompiled, and now evokes an assertion failure.
llvm-svn: 62177
|
| |
|
|
|
|
|
| |
where the argument is an apint, or smaller than the minimum
size for which there is a libcall (i32).
llvm-svn: 58994
|
| |
|
|
|
|
|
| |
codegen infrastructure, by default. Please report
any breakage to the mailing lists.
llvm-svn: 58232
|
| |
|
|
|
|
| |
LegalizeSetCCOperands are leglized. Patch by Richard Pennington.
llvm-svn: 57460
|
| |
|
|
| |
llvm-svn: 56225
|
| |
|
|
| |
llvm-svn: 54516
|
| |
|
|
| |
llvm-svn: 54512
|
| |
|
|
| |
llvm-svn: 54511
|
| |
|
|
| |
llvm-svn: 54510
|
| |
|
|
| |
llvm-svn: 54509
|
| |
|
|
| |
llvm-svn: 54508
|
| |
|
|
| |
llvm-svn: 54507
|
|
|
I had a lot of simple local codegen tests and they are now ready to be placed
in test/CodeGen.
llvm-svn: 54506
|