similar to: [LLVMdev] c++ frontend bugs

Markus F.X.J. Oberhumer schrieb: > Stefan Strasser wrote: > >> I've encountered a few bugs including ICE and reject-valid when >> compiling a program with llvmg++ which compiles fine with standalone g++. >> >> Should I report those to your bugzilla or is it likely that these bugs >> are gcc bugs in the version of gcc you're using? >> if so, are

Markus F.X.J. Oberhumer schrieb: > The reason behind this is that llvm-gcc is based on a pre-3.4 snapshot > ("3.4-llvm 20030924") then it's not unlikely that these are llvm bugs since my code also compiles with gcc 3.3 filed PR 551 and 552 -- Stefan Strasser

On Nov 19, 2004, at 9:25 PM, Mohd-Hanafiah Abdullah wrote: > Dear Dr Vikram: > > I need to know how to invoke llvmg++ so that it generates C code. Here's how you can do a single file (i.e., an unlinked executable): llvmg++ -c infile.cpp -o - | llc -march=c -o infile.cbe.c Reid might be able to tell you how to do it with a single command using the llvmc tool. In future, please

Hi! On 2020-06-16 12:37 -0000, Stuart Henderson wrote: > On 2020-06-15, Alexander Strasser <eclipse7 at gmx.net> wrote: > > I had some imap crashes (sig11) starting at the end of 2019 after > > an upgrade of dovecot. > > > > I found out, that I didn't have any problems using version v2.3.8, > > but any version v2.3.9 and higher would trigger the crashes.

in case you're interested in having llvm in debian sarge: it was removed today. I don't know why, but you might want to find out because sarge is in freeze phase for release next month. regards, -- Stefan Strasser

On Mon, 28 Jun 2004, Surupa Biswas wrote: > I am at the University of Maryland, College Park, working with Prof. > Rajeev Barua. Someone just told me that LLVM includes a C++ to C > source-to-source compiler. I was hoping you could tell me something about > that - I am trying to run some C++ benchmarks on the Motorola Mcore > simulator and my compiler only has a C front-end. Yup,

hi, when build test echo.cpp using "llvmg++ echo.cpp -o echo" it create an echo file, contain: ------------------------------------- [yue at RH9 Shootout-C++]$ cat echo #!/bin/sh lli \ -load=/usr/lib/libm.so \ $0.bc $* --------------------------------------- and using "llvmgcc echo.cpp -o echo-c", it creates an echo-c file, contain:

Adam, I recant my previous message. I built FreeType with GCC not LLVMGCC by accident (I shoulda checked!). The thing is, FreeType's makefiles don't respect environment variables. So, I did this: CC=/path/to/llvmgcc CXX=/path/to/llvmg++ configure make and was able to reproduce the problem. Not sure what's up with that but as Misha pointed out, llvmgcc isn't any

hi, I try to build hello.cpp using both llvmg++ and GNU g++, the generate llvm bytecode's size is about 960K, and the size of binary code generated by g++ is only 13K. Could anyone explain the difference between the two result? BWT: I rebuild the cfrontend in RH linux9.0, but when I build the hello.cpp the llvmG++ reports warnings too, it shows: ----------------------------- [yue at RH9

Hi Reid Spencer, > CC=/path/to/llvmgcc CXX=/path/to/llvmg++ configure > make > > and was able to reproduce the problem. Not sure what's up with that but > as Misha pointed out, llvmgcc isn't any "particular" version of 3.4, its > just 3.4ish. I also concur with him that you should file a bug and > attach the pre-processed source to it. You can get that with

hi, when i build hello.cpp, it show following conflict: ----------------------------------------------------------- [yue at RH9 Shootout-C++]$ llvmg++ hello.cpp -o hello WARNING: Type conflict between types named 'struct._Unwind_Exception'. Src='{ ulong, void (uint, \4 *) *, uint, uint }'. Dest='{ ulong, void (ubyte, \4 *) *, uint, uint }' gccld: error linking in

Hi all, After successfully building llvm tools-only and cfontend, I went back to llvm directory and ran configure --with-llvmgccdir=$CFEINSTALL Unfortunately, at the end of the process I got the following configure: WARNING: ***** llvm C/C++ front end was not found, or does not configure: WARNING: ***** appear to be working. And I do have CFEINSTALL environment variable.... BTW, I have noticed

On Wed, 6 Oct 2004, Alex Vinokur wrote: > > have less impact than for a CPU bound program). In any case, I've added > > this program to the LLVM testsuite as > > SingleSource/Benchmarks/Misc-C++/bigfib.cpp, so we should have numbers for > > it generated every night on multiple platforms. > > > [snip] > > Newsgroup

"Chris Lattner" <sabre at nondot.org> wrote in message news:Pine.LNX.4.44.0410061044190.367-100000 at nondot.org... > On Wed, 6 Oct 2004, Alex Vinokur wrote: > > > have less impact than for a CPU bound program). In any case, I've added > > > this program to the LLVM testsuite as > > > SingleSource/Benchmarks/Misc-C++/bigfib.cpp, so we should have

On Sun, 2004-12-19 at 22:52, Adam Warner wrote: > Hi Reid Spencer, > > > CC=/path/to/llvmgcc CXX=/path/to/llvmg++ configure > > make > > > > and was able to reproduce the problem. Not sure what's up with that but > > as Misha pointed out, llvmgcc isn't any "particular" version of 3.4, its > > just 3.4ish. I also concur with him that you

Hi devels, there are two issues concerning invoking optimizations: 1. this document: http://llvm.cs.uiuc.edu/docs/GettingStarted.html is very nice, it would be good though to add in a section An Example Using the LLVM Tool Chain examples on optimization step. 2. If i am not wrong there is no tool, which integrates all steps: llvmgcc->opt->llc into something like llcc (and

Hi all! This is my first post on this list. Please pardon me if I overlooked or misunderstood some things. I had some imap crashes (sig11) starting at the end of 2019 after an upgrade of dovecot. I found out, that I didn't have any problems using version v2.3.8, but any version v2.3.9 and higher would trigger the crashes. After investigating more deeply and creating a core dump, I saw that

On 2020-06-16 20:32 +0200, Alexander Strasser wrote: > On 2020-06-16 12:37 -0000, Stuart Henderson wrote: > > On 2020-06-15, Alexander Strasser <eclipse7 at gmx.net> wrote: > > > I had some imap crashes (sig11) starting at the end of 2019 after > > > an upgrade of dovecot. > > > > > > I found out, that I didn't have any problems using version

Conditional Inference Procedures in a Permutation Test Framework The `coin' package implements a general framework for conditional inference procedures, commonly known as permutation tests, theoretically derived by Strasser & Weber (1999). The conditional expectation and covariance for a broad class of multivariate linear statistics as well as the corresponding multivariate limiting

Conditional Inference Procedures in a Permutation Test Framework The `coin' package implements a general framework for conditional inference procedures, commonly known as permutation tests, theoretically derived by Strasser & Weber (1999). The conditional expectation and covariance for a broad class of multivariate linear statistics as well as the corresponding multivariate limiting