similar to: [LLVMdev] debug intrinsic documentation

Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] debug intrinsic documentation"

2006 Sep 02
2
[LLVMdev] gfortran calling convention
The NIST F77 test suite doesn't seem to be compatible with gfortran at all, so I had to work from my own sample codes, and generate test cases from them. Here's what works now, and I have a separate test case for each of these: statement functions intrinsic functions (print, cos, etc) loops, goto statments scalarized array operations function calls with *no arguments* simple common
2006 Sep 02
0
[LLVMdev] gfortran calling convention
On Fri, 1 Sep 2006, Michael McCracken wrote: > Here's what works now, and I have a separate test case for each of these: > > statement functions > intrinsic functions (print, cos, etc) > loops, goto statments > scalarized array operations > function calls with *no arguments* > simple common blocks Great! > Function calls with more than one argument don't work.
2010 Feb 11
1
Sweve/cacheSweave
Hi there I have a problem with using Sweave in combination with the option driver = cacheSweave. Whichever code I try to run - when it comes to converting the tex file into pdf it comes up with the same errors (\csname \endcsname errors). Does anybody have an idea what it going wrong? > Sweave("pgfSweave-example.Rnw",driver = cacheSweaveDriver) Writing to file
2019 Feb 28
1
Re: virt-v2v: default graphics driver for SUSE guests
Hi Pino, On 2/26/19 5:52 PM, Mike Latimer wrote: > On 2/21/19 3:07 AM, Pino Toscano wrote: >> My question is: is using cirrus still the best choice for SUSE guests? >> If not, what about using qxl as well, as done for any non-SUSE guest? >> (We can also do that depending on the version of the guest, in case >> only newer SUSE versions work fine with qxl). > At the
2006 Apr 03
0
[LLVMdev] lli: problem finding external symbol
On Mon, 3 Apr 2006, Michael McCracken wrote: > the bytecode with lli - I get the following error: > > $ lli -load=/home/mmccrack/linux/lib/libTau.sh leo-inline-300-tau.bc > ERROR: Program used external function > '__llvm_cxxeh_allocate_exception' which could not be resolved! This is most likely because you are trying to link with llvmgcc, not with llvm-g++. Make sure that
2006 Mar 21
0
[LLVMdev] problem loading analysis results from Inliner pass
A On 3/21/06, Michael McCracken <michael.mccracken at gmail.com> wrote: > On 3/21/06, Chris Lattner <sabre at nondot.org> wrote: > > On Mon, 20 Mar 2006, Michael McCracken wrote: > > > > > Hi, I'm trying to access an analysis pass from the Inliner pass, and > > > I'm having a lot of trouble getting that to work - I can verify that > >
2007 Aug 21
0
[LLVMdev] Problems building llvm-gcc-4.2 on ppc32, OS X 10.4.10
Hi, I'm guessing that no one has tried this exact combination yet. I'm trying to build the gcc4.2 front end with current LLVM SVN on a G4 Powerbook running 10.4.10. I started with this: ../gcc4.2-trunk/configure --prefix=$HOME/Documents/hpcl/LLVM/llvm-gcc-4-2/install --enable-llvm=$HOME/Documents/hpcl/LLVM/llvm-svn-obj/ --with-gmp=$HOME/Documents/hpcl/LLVM/llvm-gcc-4-2/libdeps
2006 Apr 03
2
[LLVMdev] lli: problem finding external symbol
Hi, I have a large-ish application I'm trying to build with LLVM, so I replaced g++ in the Makefiles with llvm-g++. This appears to work fine when I pass -Wl,-native to generate an ELF executable, but I want to control the inlining threshold it uses, so I am now passing -Wl,-disable-inlining and -Wa,-disable-inlining, and having it generate LLVM bytecode, then running opt -inlining to generate
2004 Sep 15
2
Routestopped
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello I try to setup a bridge firewall base on http://shorewall.net/bridge.html I''m using shorewall-1.4.10g-1. I doublecheck on /etc/shorewall/routestopped file on my firewall, and there is no "OPTIONS" options. Should I use different shorewall version ? Thanks -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux)
2006 Sep 01
0
[LLVMdev] gfortran: patch, question
On 9/1/06, Michael McCracken <michael.mccracken at gmail.com> wrote: > On 9/1/06, Chris Lattner <sabre at nondot.org> wrote: > > On Fri, 1 Sep 2006, Michael McCracken wrote: [snip] > Now f951 doesn't crash when compiling, but still can't compile the > libgfortran files. It now finds some syntax errors in a generated file > that's part of the intrinsics
2005 Aug 24
1
[LLVMdev] Problems running dejagnu tests
OK, that explains it. I probably didn't have runtest installed the last time I ran configure, and re-syncing with CVS also caused it to reconfigure, solving the problem but confusing me. Thanks, -mike On 8/24/05, Chris Lattner <sabre at nondot.org> wrote: > On Wed, 24 Aug 2005, Michael McCracken wrote: > > I'm mostly up to date, but not completely current with CVS. Is this
2005 Oct 20
1
[LLVMdev] llvm-test Makefile question
Hi, I am trying to do something similar to the profiling target in the llvm-test suite makefiles, but I'm not a gmake expert, so I am stumped on something: I did some copy-and-paste of the profile code in llvm-test/Makefile.programs and got it working within SingleSource/Benchmarks, where I can say 'make pmf' or 'make profile' and get a build with profiling results or my own
2005 Sep 17
0
[LLVMdev] Re: Problems Cross Compiling for x86 and ia64
OK, I noticed a few problems with my previous email, so I will boil the question down: What I want to do is compile for x86 and ia64 from darwin. I also want to load my own passes into opt and llc. Should I be using llvmc at all here, or should I be doing something like llvmgcc -> gccas -> opt -> llc ? I've given up on the filetype=obj argument, so now the problem is that llc is
2007 Apr 12
0
[LLVMdev] Compiler name: Nāga
On Apr 12, 2007, at 12:57 PM, Michael McCracken wrote: > Hi, the idea of a dragon theme reminded me of the dragon-like serpents > called "Nāga" from Cambodian mythology, among other places. Interesting, my only comment is if we pick this we need to just spell it Naga. Naga are also snake people in D&D (yea... I know). > > Here's a brief link explaining the
2006 Sep 11
0
[LLVMdev] gfortran calling convention
On 9/11/06, Chris Lattner <sabre at nondot.org> wrote: > On Mon, 11 Sep 2006, Michael McCracken wrote: > >> be though. > > > > I'm thinking that effort on 4.0.1 gfortran is not worthwhile, since > > 4.0.1 fails to compile some pretty basic examples, and there are some > > pretty extensive changes between then and 4.2. > > ok > > >>
2016 Oct 28
1
Disk near failure
On Fri, October 28, 2016 11:50 am, Alessandro Baggi wrote: > Il 28/10/2016 16:28, Valeri Galtsev ha scritto: >> >> On Fri, October 28, 2016 2:42 am, Alessandro Baggi wrote: >>> Il 27/10/2016 19:38, Yamaban ha scritto: >>>> For my personal use I would replace that Drive asap. >>>> - There is no warranty for it anymore (time since buy) >>>>
2006 Sep 09
1
[LLVMdev] gfortran: link error building gfortran on linux
Hi, in trying to build an llvm-gfortran on linux from today's gcc4 SVN, I get the following link errors that didn't show up on OS X. This is also using LLVM CVS from this morning. They appear to mostly be related to CodeWarrior compatibility code, but a couple are less obvious. What's the best way to fix this? I'm stuck without my powerbook for at least three weeks and I'd
2007 May 15
2
[LLVMdev] FORTRAN compiler status?
I just noticed this - I can't promise any particular amount of TLC, but I'll certainly be giving the Fortran front-end some attention as soon as LLVM moves to gcc 4.2. For future reference, does anyone know of a good free Fortran compiler test suite? Cheers, -mike On 5/14/07, Duncan Sands <baldrick at free.fr> wrote: > Hi Duraid, > > > Does anyone know what the
2005 Aug 24
3
[LLVMdev] Problems running dejagnu tests
I'm having troubles running the test suite on OS X 10.4. Inside my objdir, 'make check' gives this: % make check llvm[0]: Running test suite
2016 Sep 04
1
Please update GPG signature to long format.
Hi Michael and Dirk, there are raising concerns that, as of today's computing power, an attacker can generate a GPG key that has the same short ID as a target key. In this situation, it may be possible that a user downloads and trusts the attacker's GPG key, and as a consequence installs malware. For that reason (better explained in http://lwn.net/Articles/697417/), it is recommended to