similar to: [LLVMdev] LLVM 1.4 uploaded to Debian unstable

On Fri, 11 Mar 2005, Al Stone wrote: > So. I _finally_ got the building and packaging of LLVM and the > GCC FE into a state I'm more or less happy with. As a result, I > uploaded x86 packages into the NEW queue just a little while ago. > Whew. Nice! Thanks a lot Al! -Chris > What this means is that in a few weeks (hard to say how long, > really) the package will be

On Wed, 2005-06-01 at 10:04 -0500, Misha Brukman wrote: > On Wed, Jun 01, 2005 at 10:50:35AM -0400, Bill Wendling wrote: > > It didn't look like there was a cftonend binary for the IA-64 > > platform. Are we supposed to use the x86 binaries instead? > > The answer to that is that we don't have IA-64 in-house, so we don't > provide an IA-64 C/C++ front-end, but

Anyone willing to do some testing? I've finally gotten LLVM 1.4 to build Debian packages from source (it weren't pretty), at least for i386. To get the debs, add the following to your sources.list: deb http://toolchain.org/~ahs3 / deb-src http://toolchain.org/~ahs3 / then 'apt-get update' as usual. To install the packages: apt-get install llvm llvm-doc This will

So, I'm trying to build everything from source for the Debian package for LLVM, including the C/C++ front end. I'm running this build on LLVM 1.4 source (the released tarball), using Debian unstable (gcc 3.3.5, on a 2.6.8 kernel, on an x86_64 box, dual CPU). Before I get _too_ deep into it, I thought I would ask if the following compilation failure on the CFE looks the least bit familiar

yes, so this happens on anything that uses a struct for va_list (like alpha). I am currently working on fixing this. if you look at the last patch to the alpha portion of llvm-gcc, you can see a quick hack to work around that (aka, get it to compile), but the resultant compiler will have issues with varargs. Alternately, build ia-32 binaries on x86_64, llvm-gcc is happy with the the abi there.

On Sun, 2006-10-29 at 19:39 -0500, Adam Goode wrote: > Hi, > > I'm still working on the Fedora Extras package for LLVM. > > Because of the Fedora requirement that all packages in Extras be built > from source, I must build the dreaded C Front End. :) > > I think I've mostly got things set up correctly, but I've found what I > suspect is a tricky problem:

On Thu, 10 Mar 2005, Andrew Lenharth wrote: > yes, so this happens on anything that uses a struct for va_list (like > alpha). I am currently working on fixing this. if you look at the last > patch to the alpha portion of llvm-gcc, you can see a quick hack to work > around that (aka, get it to compile), but the resultant compiler will > have issues with varargs. While Andrew is

On Wed, Jun 01, 2005 at 10:50:35AM -0400, Bill Wendling wrote: > It didn't look like there was a cftonend binary for the IA-64 > platform. Are we supposed to use the x86 binaries instead? The answer to that is that we don't have IA-64 in-house, so we don't provide an IA-64 C/C++ front-end, but if someone were to contribute it to us, we would gratefully host it. Note that if you

Hi Misha, On 6/1/05, Misha Brukman <brukman at uiuc.edu> wrote: > On Wed, Jun 01, 2005 at 10:33:39AM -0400, Bill Wendling wrote: > > What's the plan for support on Linux 64-bit machines? Is that actively > > being worked on right now or is there a roadmap for doing this? > > Do you mean compiling on 64-bit Linux or generating code for 64-bits? > I meant

Hi, I'm still working on the Fedora Extras package for LLVM. Because of the Fedora requirement that all packages in Extras be built from source, I must build the dreaded C Front End. :) I think I've mostly got things set up correctly, but I've found what I suspect is a tricky problem: make[1]: Leaving directory `/home/adam/rpmbuild/BUILD/llvm-1.8/llvm-gcc4-obj/gcc' Checking

I'm not a Debian user, so I can't help by testing, but I do have some comments... On Tue, Jan 18, 2005 at 03:59:07PM -0700, Al Stone wrote: [snip] > If you want to install the packages one at a time, do the > following, in this order: > > apt-get install llvm-libs > apt-get install llvm-cfe > apt-get install llvm > apt-get install llvm-doc [snip I

In trying to package up LLVM for Debian, it appears that x86_64 is no longer a supported architecture -- so, my first question is, is that correct? Best I can tell, the only thing that's supposed to work for x86_64 is the C backend. For Debian, I need to build everything from scratch. When trying to build llvm-gcc4 from source, though, I get part way through the build and am told that

The LLVM 3.0 release branch has been tagged. You may now commit patches at your leisure. Thank you for keeping the ToT healthy! -bw

On Fri, 11 Mar 2005, Markus F.X.J. Oberhumer wrote: > Chris Lattner wrote: >> On Thu, 10 Mar 2005, Andrew Lenharth wrote: >> >>> yes, so this happens on anything that uses a struct for va_list (like >>> alpha). I am currently working on fixing this. if you look at the last >>> patch to the alpha portion of llvm-gcc, you can see a quick hack to work

Would anyone mind terribly if I tried to get LLVM packaged and added to the Debian distribution? -- Ciao, al ---------------------------- Al Stone Linux & Open Source Lab Hewlett-Packard Company E-mail: ahs3 at fc.hp.com ----------------------------

+ LLVM-dev (clang is mostly about the frontend and this is a backend failure), you may have more change to get an answer. > On Feb 6, 2017, at 5:49 AM, Gaetano Checinski via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > Running the following code with clang++ -S -emit-llvm main.cpp && lli main.ll on Linux(Debian) > > #include <future> > > int main () {

> I’ve seen the same problem, but didn’t find solution back then. > I can give a hint that it is related to a thread local storage (notice TLS in the name). > > The same result can be reproduced by this simple program: > > thread_local int x = 0; > int main() { > return 0; > } > >When compiled into IR it produces similar error: > >LLVM ERROR:

Since there was some interest in checking out Subversion and seeing if it might be helpful to the LLVM project, I went ahead and created Subversion repositories from the current CVS tree. The content of these repositories can be seen at: http://toolchain.org/websvn/ and are current as of roughly 23:03 UTC, 15 Mar 2005 (more or less). There are copies of LLVM itself, the CFE, the llvm-test

Resending :(. Any pointers? tia On 5/21/2012 2:46 PM, Ashok Nalkund wrote: > On 5/21/2012 11:15 AM, Nick Lewycky wrote: >> Ashok Nalkund wrote: >>> Resending, any pointers? I demangled the symbol and it turns out to be: >>> std::__1::locale::use_facet(std::__1::locale::id&) const >> >> My guess is that you've got a .bc file produced on a mac using

Following simple program gives different answers when compiling with GCC (4.8.4) and ToT Clang: $ cat builtin_fmodf_bugpoint.cpp #include <cstdio> int main(int argc, char** argv) { const float a = 1.0f; const float b = 0.1f; printf("%f mod %f = %f\n", a, b, __builtin_fmodf(a, b)); return 0; } $ g++ -o builtin_fmodf_bugpoint_gcc builtin_fmodf_bugpoint.cpp $