Displaying 20 results from an estimated 107 matches for "x86subtarget".
2011 May 31
0
[LLVMdev] X86Subtarget.h could be beautified
Hi!
when reading X86Subtarget.h the methods seem a bit disordered, therefore
I would
propose to sort them new:
-getTargetTriple()
-cpu features (e.g. hasSSE1())
-os types (e.g. isTargetDarwin())
-object types (e.g. isTargetELF())
-callconv related functions (e.g. isTargetWin64(), consider renaming to
isCallConvWin64(),
getS...
2006 Dec 21
1
[LLVMdev] No crt2.o file found
Hello, Matthew.
> My file size matches the patched file. I haven't figured out how to get 7-zip to give me checksum information on windows.
Use md5sum utility. It can be successfully found via google.
> I rashly copied all the *.o files from my mingw\lib directory to the llvm\lib directory.
> This does enable the hello world binary to compile and to function correctly.
Strange.
2017 Apr 27
4
-msave-args backend support for x86_64
...MFI.isFrameAddressTaken() || MFI.hasOpaqueSPAdjustment() ||
@@ -850,6 +851,25 @@
MI->getOperand(3).setIsDead();
}
+// FIXME: Get this from tablegen.
+static ArrayRef<MCPhysReg> get64BitArgumentGPRs(CallingConv::ID CallConv,
+ const X86Subtarget &Subtarget) {
+ assert(Subtarget.is64Bit());
+
+ if (Subtarget.isCallingConvWin64(CallConv)) {
+ static const MCPhysReg GPR64ArgRegsWin64[] = {
+ X86::RCX, X86::RDX, X86::R8, X86::R9
+ };
+ return makeArrayRef(std::begin(GPR64ArgRegsWin64), std::end(GPR64ArgRegsWin64));
+ }
+...
2011 Oct 16
0
[LLVMdev] Problem with X86Subtarget::IsLegalToCallImmediateAddr()
The current rule is:
/// IsLegalToCallImmediateAddr - Return true if the subtarget allows calls
/// to immediate address.
bool X86Subtarget::IsLegalToCallImmediateAddr(const TargetMachine &TM) const {
if (In64BitMode)
return false;
return isTargetELF() || TM.getRelocationModel() == Reloc::Static;
}
But this is not doing the correct thing for ELF PIC. The
straight-forward way to fix this is to change the || to &&....
2008 Mar 27
0
[LLVMdev] llvm-gcc 4.2 assertion failed on linux x86_64
Does this fix it?
Index: lib/Target/X86/X86Subtarget.h
===================================================================
--- lib/Target/X86/X86Subtarget.h (revision 48879)
+++ lib/Target/X86/X86Subtarget.h (working copy)
@@ -144,9 +144,12 @@
std::string getDataLayout() const {
const char *p;
- if (is64Bit())
- p = "e-p:64:64-...
2008 Mar 27
1
[LLVMdev] llvm-gcc 4.2 assertion failed on linux x86_64
Probably better to move the discussion to a bug?
Evan
On Mar 27, 2008, at 9:04 AM, Duncan Sands wrote:
> Does this fix it?
>
> Index: lib/Target/X86/X86Subtarget.h
> ===================================================================
> --- lib/Target/X86/X86Subtarget.h (revision 48879)
> +++ lib/Target/X86/X86Subtarget.h (working copy)
> @@ -144,9 +144,12 @@
>
> std::string getDataLayout() const {
> const char *p;
> - if (is...
2013 Nov 22
2
[LLVMdev] [PATCH] Detect Haswell subarchitecture (i.e. using -march=native)
...review of your code after that.
Tim, I don’t want to push too much. But since there’s 3.4 release on the horizon, maybe you could find a moment review this patch. Especially Haswell is all there since few months.
Cheers,
--
Adam
---
lib/Support/Host.cpp | 8 ++++++++
lib/Target/X86/X86Subtarget.cpp | 3 ++-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/lib/Support/Host.cpp b/lib/Support/Host.cpp
index 380df6b..2235456 100644
--- a/lib/Support/Host.cpp
+++ b/lib/Support/Host.cpp
@@ -138,6 +138,8 @@ std::string sys::getHostCPUName() {
// switch, then we have full AVX sup...
2012 May 24
2
[LLVMdev] use AVX automatically if present
Henning,
I believe the code that is supposed to do this is in:
lib/Target/X86/X86Subtarget.cpp in
X86Subtarget::AutoDetectSubtargetFeatures()
Is there a bug in that function?
-Hal
On Thu, 24 May 2012 23:56:48 +0200 (CEST)
Henning Thielemann <llvm at henning-thielemann.de> wrote:
>
> On Thu, 24 May 2012, Pan, Wei wrote:
>
> > Very likely AVX is not enabled in yo...
2011 Jun 15
0
[LLVMdev] Custom allocation orders
...86::DIL,
X86::R8B, X86::R9B, X86::R10B, X86::R11B,
X86::BL, X86::R14B, X86::R15B, X86::R12B, X86::R13B, X86::BPL
};
GR8Class::iterator
GR8Class::allocation_order_begin(const MachineFunction &MF) const {
const TargetMachine &TM = MF.getTarget();
const X86Subtarget &Subtarget = TM.getSubtarget<X86Subtarget>();
if (Subtarget.is64Bit())
return X86_GR8_AO_64;
else
return begin();
}
GR8Class::iterator
GR8Class::allocation_order_end(const MachineFunction &MF) const {
const TargetMachine &TM = MF.getT...
2010 Jul 05
2
[LLVMdev] Data layout hard coded for X86 target
Chris Lattner <clattner at apple.com> writes:
> On Jul 5, 2010, at 3:31 AM, Óscar Fuentes wrote:
>
>> Chris Lattner <clattner at apple.com> writes:
>>
>>> On Jul 4, 2010, at 6:43 PM, Óscar Fuentes wrote:
>>>
>>>> In X86Subtarget.h there is a method `getDataLayout' which selects the
>>>> data layout depending on the platform, ignoring whatever the user setted
>>>> with Module::setDataLayout.
>>>>
>>>> What's the rationale for this?
>>>
>>> Data layo...
2013 Sep 12
0
[LLVMdev] [PATCH] Detect Haswell subarchitecture (i.e. using -march=native)
Hi Adam,
> OK. I know the reason you cannot reproduce it, before posting
> the patch I've decided to check for AVX before checking AVX2,
> just not to cpuid AVX2 when we don't have AVX1 anyway.
I suspect it was also incompetence on my part. Given the differences
I'm seeing now I can't believe there'd be *no* difference in my tests
if I'd done them properly.
2010 Jul 05
2
[LLVMdev] Data layout hard coded for X86 target
Chris Lattner <clattner at apple.com> writes:
> On Jul 4, 2010, at 6:43 PM, Óscar Fuentes wrote:
>
>> In X86Subtarget.h there is a method `getDataLayout' which selects the
>> data layout depending on the platform, ignoring whatever the user setted
>> with Module::setDataLayout.
>>
>> What's the rationale for this?
>
> Data layout is a property of the target, not the program b...
2008 Mar 27
2
[LLVMdev] llvm-gcc 4.2 assertion failed on linux x86_64
Here you go:
Starting program: /home/chandlerc/code/compilers/build/llvm-gcc/gcc/cc1
-fpreprocessed -march=k8 testcase.i -o /dev/null
warning: no loadable sections found in added symbol-file system-supplied DSO
at 0x7fff0d5fe000
[Thread debugging using libthread_db enabled]
foocc1: /home/chandlerc/code/compilers/llvm-gcc/gcc/llvm-types.cpp:81: const
llvm::Type* llvm_set_type(tree_node*, const
2013 Nov 23
0
[LLVMdev] [PATCH] Detect Haswell subarchitecture (i.e. using -march=native)
...s AVX2 CPUID leaf 7
subleaf 0 AVX2 flag as core-avx2.
Port GetX86CpuIDAndInfoEx from X86MCTargetDesc to support x86 CPUID subleafs.
Also detect family 6 model 62 (0x3E) Ivy Bridge EP as core-avx-i.
---
lib/Support/Host.cpp | 96 ++++++++++++++++++++++++++++++++++++++---
lib/Target/X86/X86Subtarget.cpp | 7 ++-
2 files changed, 96 insertions(+), 7 deletions(-)
diff --git a/lib/Support/Host.cpp b/lib/Support/Host.cpp
index 380df6b..6e9a5c9 100644
--- a/lib/Support/Host.cpp
+++ b/lib/Support/Host.cpp
@@ -95,6 +95,75 @@ static bool GetX86CpuIDAndInfo(unsigned value, unsigned *rEAX, unsigned *r...
2008 Feb 15
1
[LLVMdev] LLVM2.2 x64 JIT trouble on VStudio build
...ed int
BytesToPopOnReturn 0 int
BytesCallerReserves 0 int
- Subtarget 0x00000000008eda90 {AsmFlavor=Intel PICStyle=None X86SSELevel=SSE2 ...} const llvm::X86Subtarget *
+ llvm::TargetSubtarget {...} llvm::TargetSubtarget
AsmFlavor Intel llvm::X86Subtarget::AsmWriterFlavorTy
PICStyle None llvm::PICStyle::Style...
2013 Sep 12
3
[LLVMdev] [PATCH] Detect Haswell subarchitecture (i.e. using -march=native)
> That's far more worrying to me than not being able to detect Haswell.
> I can't reproduce the problem here at the moment: both debug and
> release builds give identical assembly for Host.cpp.
OK. I know the reason you cannot reproduce it, before posting the patch I've decided to check for AVX before checking AVX2, just not to cpuid AVX2 when we don't have AVX1 anyway.
2013 Nov 23
2
[LLVMdev] [PATCH] Detect Haswell subarchitecture (i.e. using -march=native)
I agree with Tim, you need to implement a GetCpuIDAndInfoEx function in
Host.cpp and pass the correct value to ecx. Also you need to verify that 7
is a valid leaf because an invalid leaf is defined to return the highest
supported leaf on that processor. So if a processor supports say leaf 6 and
not leaf 7, then an access leaf 7 will return the data from leaf 6 causing
unrelated bits to be
2010 Jul 05
0
[LLVMdev] Data layout hard coded for X86 target
On Jul 5, 2010, at 3:31 AM, Óscar Fuentes wrote:
> Chris Lattner <clattner at apple.com> writes:
>
>> On Jul 4, 2010, at 6:43 PM, Óscar Fuentes wrote:
>>
>>> In X86Subtarget.h there is a method `getDataLayout' which selects the
>>> data layout depending on the platform, ignoring whatever the user setted
>>> with Module::setDataLayout.
>>>
>>> What's the rationale for this?
>>
>> Data layout is a property of the...
2011 Jun 07
2
[LLVMdev] a problem of jit debug
hi ��f��
but in the source code i find this comment.
// ELF is a reasonably sane default and the only other X86 targets we
// support are Darwin and Windows. Just use "not those".
does this means that we can debug jit on windows?
i am confused.help
2011/6/7 ��f�� <chenwj at iis.sinica.edu.tw>:
> Hi, Tang
>
>> result is correct. But on windows, i failed. Why? I build
2011 Jun 07
0
[LLVMdev] a problem of jit debug
Hi, Tang
> but in the source code i find this comment.
> // ELF is a reasonably sane default and the only other X86 targets we
> // support are Darwin and Windows. Just use "not those".
I guess you found above comment in lib/Target/X86/X86Subtarget.h.
But I think X86Subtarget.h is only related to the codegen, but NOT
the debugging information. The comment means you can generate code
for Linux, Darwin and Windows on X86.
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R....