Displaying 20 results from an estimated 336 matches for "mattrs".
Did you mean:
attrs
2008 Nov 20
4
[LLVMdev] changing -mattr behavior with mmx and sse
Hi,
When setting -mattr option on X86, I would like to treat MMX
separately from SSE levels. This would allow a client who sets the
attributes directly to set the SSE level independent of MMX, e.g., llc
-march=x86 -mattr=sse41, one would get sse4.1 with mmx disabled while
llc -march=x86 -mattr=mmx -mattr=sse42 will get mmx and sse42. If
anyone objects to this change, please let me
2008 Nov 20
0
[LLVMdev] changing -mattr behavior with mmx and sse
Might you instead consider just adding a -disable-mmx option?
Preston
On Thu, 2008-20-11 at 02:57 -0500, Mon Ping Wang wrote:
> Hi,
>
> When setting -mattr option on X86, I would like to treat MMX
> separately from SSE levels. This would allow a client who sets the
> attributes directly to set the SSE level independent of MMX, e.g., llc
> -march=x86 -mattr=sse41, one would get
2008 Nov 20
0
[LLVMdev] changing -mattr behavior with mmx and sse
On Nov 19, 2008, at 11:57 PMPST, Mon Ping Wang wrote:
> Hi,
>
> When setting -mattr option on X86, I would like to treat MMX
> separately from SSE levels. This would allow a client who sets the
> attributes directly to set the SSE level independent of MMX, e.g., llc
> -march=x86 -mattr=sse41, one would get sse4.1 with mmx disabled while
> llc -march=x86 -mattr=mmx
2008 Nov 20
1
[LLVMdev] changing -mattr behavior with mmx and sse
Hi Dale,
I will not change the default. I would dislike to see any regressions
due to this type of change.
-- Mon Ping
On Nov 20, 2008, at 10:12 AM, Dale Johannesen wrote:
>
> On Nov 19, 2008, at 11:57 PMPST, Mon Ping Wang wrote:
>
>> Hi,
>>
>> When setting -mattr option on X86, I would like to treat MMX
>> separately from SSE levels. This would allow a
2008 Nov 20
1
[LLVMdev] changing -mattr behavior with mmx and sse
On Nov 20, 2008, at 8:31 AM, Preston Gurd wrote:
> Might you instead consider just adding a -disable-mmx option?
I agree, this is a better approach. This distinguishes between
capabilities of the chip and the desire to codegen specific vectors
one way or another.
-Chris
>
> Preston
>
> On Thu, 2008-20-11 at 02:57 -0500, Mon Ping Wang wrote:
>> Hi,
>>
>>
2006 Apr 19
2
[LLVMdev] floating point exception and SSE2 instructions
On Thu, 20 Apr 2006, Simon Burton wrote:
>>> From what I remember, this is a bug in debian libc:
>> some floating point flags are set incorrectly causing SIGFPE.
>> Can't find the bug report ATM.
>
> Oh, it just showed up on numpy-discussion:
> http://sources.redhat.com/bugzilla/show_bug.cgi?id=10
>
> """
> #include <fenv.h>
> void
2013 Jan 31
2
[LLVMdev] Getting command line options to affect subtarget features
On Thu, 2013-01-31 at 09:42 -0600, Hal Finkel wrote:
> ----- Original Message -----
> > From: "Bill Schmidt" <wschmidt at linux.vnet.ibm.com>
> > To: llvmdev at cs.uiuc.edu
> > Sent: Thursday, January 31, 2013 9:26:15 AM
> > Subject: [LLVMdev] Getting command line options to affect subtarget features
> >
> > The problem I'm trying to
2013 Jan 31
2
[LLVMdev] Getting command line options to affect subtarget features
On Thu, 2013-01-31 at 11:23 -0600, Bill Schmidt wrote:
> On Thu, 2013-01-31 at 10:17 -0600, Bill Schmidt wrote:
> >
> > On Thu, 2013-01-31 at 09:42 -0600, Hal Finkel wrote:
> > > ----- Original Message -----
> > > > From: "Bill Schmidt" <wschmidt at linux.vnet.ibm.com>
> > > > To: llvmdev at cs.uiuc.edu
> > > > Sent:
2013 Jan 31
0
[LLVMdev] Getting command line options to affect subtarget features
On Thu, 2013-01-31 at 10:17 -0600, Bill Schmidt wrote:
>
> On Thu, 2013-01-31 at 09:42 -0600, Hal Finkel wrote:
> > ----- Original Message -----
> > > From: "Bill Schmidt" <wschmidt at linux.vnet.ibm.com>
> > > To: llvmdev at cs.uiuc.edu
> > > Sent: Thursday, January 31, 2013 9:26:15 AM
> > > Subject: [LLVMdev] Getting command line
2017 Sep 26
2
Difference between -mattr=+soft-float and -float-abi=soft
Hi,
I’ve run into a case where `llc -mattr=+soft-float` for
"armv7-unknown-linux-androideabi” segfaults, while
`llc -float-abi=soft` does not. Similarly if the
"target-features"="+soft-float” metadata is embedded,
llc segfaults.
I fear I’m missing something rather subtle here, could
someone help me understand the differences?
Cheers,
Moritz
2017 Sep 26
0
Difference between -mattr=+soft-float and -float-abi=soft
Hi Moritz,
On 26 September 2017 at 09:09, Moritz Angermann via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> I’ve run into a case where `llc -mattr=+soft-float` for
> "armv7-unknown-linux-androideabi” segfaults, while
> `llc -float-abi=soft` does not. Similarly if the
> "target-features"="+soft-float” metadata is embedded,
> llc segfaults.
The float-abi
2013 Jan 31
0
[LLVMdev] Getting command line options to affect subtarget features
On Thu, 2013-01-31 at 11:29 -0600, Bill Schmidt wrote:
> On Thu, 2013-01-31 at 11:23 -0600, Bill Schmidt wrote:
> > On Thu, 2013-01-31 at 10:17 -0600, Bill Schmidt wrote:
> > >
> > > On Thu, 2013-01-31 at 09:42 -0600, Hal Finkel wrote:
> > > > ----- Original Message -----
> > > > > From: "Bill Schmidt" <wschmidt at
2006 Apr 19
0
[LLVMdev] floating point exception and SSE2 instructions
On Wed, 19 Apr 2006 18:21:32 -0500 (CDT)
Chris Lattner <sabre at nondot.org> wrote:
>
>
> I don't see what this has to do with anything, but...
Me neither.
>
> > Is there a way I can disable SSE instruction generation in LLVM ?
>
> Yes. Pass -mattr=-sse1,-sse2,-sse3 to lli or llc.
Right, that fixed it.
BTW:
from the --help:
2017 Sep 26
1
Difference between -mattr=+soft-float and -float-abi=soft
Hi Tim,
Ohh, I completely forgot to attach the source. Running this with:
$ llc -O2 -mcpu=generic HeapStackCheck.ll -mattr=+soft-float -o HeapStackCheck.s
results in
0 llc 0x000000010fea65e6 llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 37
1 llc 0x000000010fea5b3a llvm::sys::RunSignalHandlers() + 83
2 llc
2011 Sep 03
2
[LLVMdev] The right option combination to compile into ARM/Thumb2 code.
Hello,
I'm trying to convince llc to compile into thumb2 ISA on ARMv7. I'm using:
-march=thumb -mattr=v7,thumb2,vfp3
but llc complains about this with:
llc: error: invalid target 'thumb -mattr=v7,thumb2,vfp3'
I'm using LLVM from Aug 29 2011. To me the set of options looks sane so
I'd like to ask what's wrong with this.
Thanks!
Karel
2013 Jan 31
2
[LLVMdev] Getting command line options to affect subtarget features
The problem I'm trying to solve: Invoking clang on PowerPC with
-fno-altivec has no effect.
>From what I've been able to piece together, PPC.td specifies various
CPUs and the processor features available on each. So for example we
have:
def FeatureAltivec : SubtargetFeature<"altivec","HasAltivec", "true",
2013 Jan 31
0
[LLVMdev] Getting command line options to affect subtarget features
----- Original Message -----
> From: "Bill Schmidt" <wschmidt at linux.vnet.ibm.com>
> To: llvmdev at cs.uiuc.edu
> Sent: Thursday, January 31, 2013 9:26:15 AM
> Subject: [LLVMdev] Getting command line options to affect subtarget features
>
> The problem I'm trying to solve: Invoking clang on PowerPC with
> -fno-altivec has no effect.
>
> From what
2011 May 06
2
[LLVMdev] [PATCH ]Add Subtarget ptx23
Hi, Justin
PTX version in CUDA 4.0 has changed from 2.2 to 2.3.
I add ptx23 subtarget and update a testcase.
Is that O.K.?
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667
-------------- next part --------------
Index: test/CodeGen/PTX/options.ll
2011 Sep 03
0
[LLVMdev] The right option combination to compile into ARM/Thumb2 code.
Hi Karel,
It actually looks like the argument parser has parsed "thumb -mattr=v7,thumb2,vfp3" as the full argument to "-march=". Strange.
The easiest way to get what you want is probably "-mtriple thumbv7--". v7 has Thumb2 enabled and VFPv3 (along with NEON) by default.
Cheers,
James
________________________________________
From: llvmdev-bounces at cs.uiuc.edu
2020 Mar 27
3
llvm-objdump cannot recognize mul&mulh RISC-V M Instructions
I am using llvm-project compiling risc-v programs.
llvm-project version:dd8a2013dc1804be1b7d9cffacad2e984300bd22
Instructons to build LLVM+clang:
```
cmake -G Ninja
-DCMAKE_INSTALL_PREFIX=/home/llvm/workspace/llvm/llvm-project/llvm_install
-DCMAKE_BUILD_TYPE="Release"
-DDEFAULT_SYSROOT="/home/llvm/workspace/riscv/riscv-tc-20200220/bin/riscv32-unknown-elf"