diff options
| author | Daniel Sanders <daniel.sanders@imgtec.com> | 2016-06-06 12:02:21 +0000 |
|---|---|---|
| committer | Daniel Sanders <daniel.sanders@imgtec.com> | 2016-06-06 12:02:21 +0000 |
| commit | 0ca86fe84dc916b9af9c70c1d1163298e1928993 (patch) | |
| tree | 23c6e17dca1e70ccc5a0f32ebf0c27dc61df9061 /llvm/lib/Target/WebAssembly/WebAssemblyMachineFunctionInfo.h | |
| parent | 3528832930542732d9defefb97e242f03fb5bd5c (diff) | |
| download | llvm-0ca86fe84dc916b9af9c70c1d1163298e1928993.zip llvm-0ca86fe84dc916b9af9c70c1d1163298e1928993.tar.gz llvm-0ca86fe84dc916b9af9c70c1d1163298e1928993.tar.bz2 | |
[mips] The default ABI depends on the CPU not the Arch on MTI and IMG vendor triples.
Summary:
32-bit CPU's default to O32. 64-bit CPU's default to N64. The default CPU
(mips32r2/mips64r2) still depends on the arch so there's no functional
change when the CPU isn't specified but commands like:
clang -target mips-mti-linux-gnu -mips64r2
will now default to a 64-bit ABI like our gcc toolchains do* instead of
asserting in the backend**.
Other vendors (including Triple::UnknownVendor) still derive the default
ABI from the arch.
* Although not the same one as our gcc toolchains, clang has historically
defaulted to N64 where gcc defaults to N32.
** Mixing O32 and a 64-bit CPU causing assertions is a long-standing bug.
Reviewers: atanasyan
Subscribers: sdardis, cfe-commits
Differential Revision: http://reviews.llvm.org/D21016
llvm-svn: 271884
Diffstat (limited to 'llvm/lib/Target/WebAssembly/WebAssemblyMachineFunctionInfo.h')
0 files changed, 0 insertions, 0 deletions