similar to: [LLVMdev] Enable soft-float

On 3/31/11 8:39 PM, Xun Li wrote: > Hi All, > > I am working on a custom defined architecture which implements Sparc > ISA but without floating point instructions. > I have two questions regarding using LLVM: > 1. How to enable soft-float when building llvm-gcc? There might be an option when configuring llvm-gcc. Check the GCC docs to see if such an option exists. Maybe

On Thu, Mar 31, 2011 at 6:47 PM, John Criswell <criswell at illinois.edu> wrote: > On 3/31/11 8:39 PM, Xun Li wrote: >> >> Hi All, >> >> I am working on a custom defined architecture which implements Sparc >> ISA but without floating point instructions. >> I have two questions regarding using LLVM: >> 1. How to enable soft-float when building

Hi, I was trying to use llc with soft-float option to generate soft-float code for Sparc. But it does not work. With or without -soft-float option will generate the same code for llc. Is this still an experimental feature? -- Xun Li Computer Architecture Lab Department of Computer Science University of California, Santa Barbara

Hi, > > llvm-gcc assumes that there's already a native code C library available to > > use. 鼦ll the systems of which I know already come with a C library. 狢f you > > somehow don't have a C library for your system, you'll have to compile one. > > > > Yes every system comes with C library implementations but if the > target architecture is different

Hi, Since LLVM does not contain an assembler and linker to generate native code, do people have to write their own assembler if the target is different from the host? Or did I misunderstand something? Thanks. Xun Li ArchLab Department of Computer Science University of California, Santa Barbara

Hi, I'm trying to generate some SPARCv8 assembly for a sparc target that doesn't have an FPU. I'm unable to get the flow to generate calls to a soft-float library. Since I wasn't able to find a definitive answer, I was hoping someone might be able to offer some pointers or shed some light. Running "clang -c -emit-llvm -msoft-float test.c -o test.bc" doesn't generate

The documentation is correct, and the observation that the IR verifier is currently not verifying this property is also correct. Due to the way that dbg.declares are handled by later stages, LLVM can only keep track of one dbg.declare per variable and that is intentional. The dbg.declare intrinsic is supposed to pin a variable to a stack slot, such as in the code that clang emits at -O0. If you

On Oct 31, 2008, at 1:10 PM, Luke Dalessandro wrote: > I've started trying by trying to get sparc-sun-solaris2.10 (niagara) > working. It appears that neither llvm nor llvm-gcc will build natively > on the system, so I think that I need to build an llvm-gcc cross > compiler. Get a gcc binary from someplace, use that to then build it, then install and use that, presto, done,

Hi Xun, On 16/09/13 03:42, Xun Chen wrote: > Hi, Guys: > > I'm new for LLVM. Just downloaded the LLVM. > I used cmake to compiler the LLVM3.3, but found an error, because it can > not automatically compiler the target description file (*.td) to the .inc file. > But when I tried the LLVM 3.2, It is ok. > Could your give me some suggestion? your description

Please review the enclosed patch for Sparc debug info. I have been able to view source files, set breakpoints, and single step source lines after applying this patch. I can't view variables because I haven't implemented Dwarf type data, yet. -Rich -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: sparcdebug.patch URL:

On Sep 6, 2009, at 1:34 PM, Richard Pennington wrote: > Please review the enclosed patch for Sparc debug info. > I have been able to view source files, set breakpoints, and single > step source lines after applying this patch. I can't view variables > because I haven't implemented Dwarf type data, yet. Cool! I'm glad to see progress on the sparc backend: +++

Hi, Guys: I'm new for LLVM. Just downloaded the LLVM. I used cmake to compiler the LLVM3.3, but found an error, because it can not automatically compiler the target description file (*.td) to the .inc file. But when I tried the LLVM 3.2, It is ok. Could your give me some suggestion? Regards' Xun -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

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

> I am new to LLVM, and I'm trying to compile llvm and llvm-gcc from > subversion on a Solaris10/SPARC machine. I have already tried building > llvm-2.4 on this machine, but it failed. That's correct. There was a bug fixed after 2.4 release. > Since then I am trying to build llvm-gcc and it fails all the time. I > tried building llvm-gcc from svn and 2.5 pre-release. I also

I just updated my quad-processor X64 machine (AMD Phenom(tm) II X4 945 Processor) to the latest CentOS 5 xen kernel (2.6.18-371.4.1.el5xen) and I am getting occasional "BUG: soft lockup - CPU#n stuck for X s! [swapper:0]" messages. I did some net searching, and found some bugzilla reports (https://bugzilla.redhat.com/show_bug.cgi?id=649519 and http://bugs.centos.org/view.php?id=4488),

I am trying to do some research that involves instrumenting LLVM IR, that I need to test for performance and scalability on a bunch of systems. I've started trying by trying to get sparc-sun-solaris2.10 (niagara) working. It appears that neither llvm nor llvm-gcc will build natively on the system, so I think that I need to build an llvm-gcc cross compiler. The documentation for building

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1341839122 -7200 # Node ID 2dd50c201ca0d3542f3589942ae9e51d33ec7509 # Parent 42f76d536b116d2ebad1b6705ae51ecd171d2581 stubdom: fix errors in newlib rpmlint found a few code bugs in newlib, and marks them as errors after rpm build. Add another newlib patch and apply it during stubdom build. I: A function uses a

Hi, In the LLVM documentation it says "there can only be one call to llvm.dbg.declare for a given concrete local variable." However we don't seem to be checking it. opt tool can process IR that violates this rule without complaining. Is this intended, or is it a bug? What would be the consequence when this constraint is broken? -- Xun

Hi all, -soft-float can not be rightly use by llc. All float function operation will call soft float, but not hard. My mips device cannot support half float type, so I hack the llvm, and add soft half float and add -soft-float option. I add the function define for __gnu_f2h_ieee() and __gnu_h2f_ieee (), and it can call the soft half float. However, all the others function about