similar to: Using binary versions of release candidates...

On Sat, 6 May 2017 23:11:16 +0800 C Bergström <cbergstrom at pathscale.com> wrote: > On Sat, May 6, 2017 at 11:07 PM, Perry E. Metzger via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > Howdy! > > > > I've noticed that requests for help by people like me who are > > developing front ends are often lost in the noise in the llvm-dev > >

On Sat, 6 May 2017 13:46:18 -0700 Sanjoy Das via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I'm not sure that will work well, because people won't usually > > wait a week to get their questions before moving on. If you're > > actively working full time on a project, you probably want > > answers in much less time. > > Sure s/week/day/ then.

On Sat, 6 May 2017 21:38:50 -0700 Sanjoy Das <sanjoy at playingwithpointers.com> wrote: > Hi Perry, > > On Sat, May 6, 2017 at 2:55 PM, Perry E. Metzger > <perry at piermont.com> wrote: > >> Let me put it this way -- I'm pretty sure if you take it on > >> yourself to answer beginner questions on llvm-dev promptly, > >> nobody will *complain*.

On Sat, 6 May 2017 12:06:03 -0700 Sanjoy Das <sanjoy at playingwithpointers.com> wrote: > Hi, > > On Sat, May 6, 2017 at 11:31 AM, Perry E. Metzger via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > It makes sense to have a place for us to talk to each other where > > we're the dominant traffic, where our questions for each other > > aren't

On Sun, 7 May 2017 00:01:34 +0800 C Bergström <cbergstrom at pathscale.com> wrote: > > Having a place dedicated to mutual aid among front end developers > > (and of course assistance from anyone else who is willing to > > answer questions) would be nice. > > > > I referred you to that list in speaking from experience. cfe-dev > may have started life as a

Howdy! I've noticed that requests for help by people like me who are developing front ends are often lost in the noise in the llvm-dev list. Although LLVM is a wonderful and very productive framework, I've found that getting help on my front end has been very difficult, and learning necessary detail about the APIs and the like is often very, very challenging. Perhaps it would be good to

I'm experimenting with a 2.0 setup, using the sieve plugin for 2.0 from mercurial. Without sieve, everything seems to work fine. Once I put in a .dovecot.sieve file, though, nothing gets delivered, with the only hint of what's going wrong being this mess in syslog: Jul 7 13:18:00 bellman dovecot: lda(perry): Panic: file index-transaction.c: line 70 (index_transaction_init): assertion

It appears that the lda + sieve does not respect the userdb_mail setting, though the imap server does(!?). Is this expected behavior? Perry -- Perry E. Metzger perry at piermont.com

Pardon the length of this reply, but it seemed useful to be explicit about my concerns. On Sun, 7 May 2017 00:55:51 +0800 C Bergstrom <cbergstrom at pathscale.com> wrote: > You don't seem to be listening, but one last try. I listened. I respectfully disagree. > If you have a FE related question - Ask on cfe-dev and if you don't > get a response I'd be surprised. I

On Thu, 11 May 2017 20:14:11 +1000 Dean Michael Berris via llvm-dev <llvm-dev at lists.llvm.org> wrote: > FWIW, I think the "modern" way of doing any of this is with any one > of the following services (that don't need to be owned/maintained > by the LLVM Foundation): > > - Stack Overflow (maybe if it gets large enough, get a "vertical" > for just

Searching the archives there has been some discussion about the need for QOS routing on a mixed voice data broadband like ADSL. Has anyone run * on a production system with voice and data. Can anyone share what has to be done to secure the voice and throttle back the data? If a linux router is need can that run on the * box to reduce cost? All help is gratefully received, so I can plan a

Hi All, First of all, I am not native English speaker. While reading BUILD_VECTOR related code, for example, PPCTargetLowering::LowerBUILD_VECTOR, I see "splat" here and there. Could someone explain what it is (does splat mean the same thing across the whole code base)? Besides, from my English dictionary, I don't know why we call such thing as "splat"... :p Regards,

Hi, Currently, I can build lld/llvm on Fedora 17 but fail to build it on iMac. The commands I use as follows. Anyone can help me? Or is there the lld mail list I can post the question? Linux/Fedora can be built by the following command cmake -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_FLAGS=-std=c++11 -DCMAKE_BUILD_TYPE=Debug -G "Unix Makefiles" ../src/ make iMac

2015-03-29 3:33 GMT-05:00 Ed Schouten <ed at 80386.nl>: > I am cross-compiling compiler-rt for my specific use-case. That said, > I'm cross-compiling from x86-64 to x86-64, but for a different ABI. > This is what I use: > > > https://github.com/NuxiNL/cloudlibc/wiki/Building-runtime-libraries#user-content-compiler-rt > > -DCMAKE_CROSSCOMPILING=True > > As

On 04/12/2019 06:31 PM, Tom Stellard via llvm-dev wrote: > On 04/12/2019 04:28 PM, AiChi via llvm-dev wrote: >> Hi, >> >> I'm currently working on one of my team's project to build LLVM full clang toolchain (Clang, libcxx, libcxxabi) on a CentOS machine. >> >> Previously we compiled our codebase with llvm-toolset-7/clang++, which by default takes stdlibc++

Hi! I'm trying to build a fast Clang for myself to use for debug builds on Clang itself, but I've been struggling for a very long time on it. Could you please help? I've been following this guide: https://llvm.org/docs/HowToBuildWithPGO.html I've quickly learned that its outdated, because the script it talks about doesn't work with the monorepo layout at all, but in any

Le 8 août 2013 à 07:22, gamma_chen <gamma_chen at yahoo.com.tw> a écrit : > Hi, > > Currently, I can build lld/llvm on Fedora 17 but fail to build it on iMac. The commands I use as follows. Anyone can help me? Or is there the lld mail list I can post the question? > > Linux/Fedora can be built by the following command > cmake -DCMAKE_CXX_COMPILER=clang++

1) Build clang with GCC-4.9.2, when compling other application s with clang/clang++, the default linker is ld, can I replace it with other linker tool， if we can, how to do it? I.E. can we use collect2 instead? 2) how to specify the path, if we do not use the default vertion GCC? Best Regards! Eric Lew -------------- next part -------------- An HTML attachment was scrubbed... URL:

Yes, that was it! Now that I took a closer look, the guide also states that I should use the stage2 build. Silly me. Thanks! On Tue, 3 Sep 2019 at 19:31, David Blaikie <dblaikie at gmail.com> wrote: > I /guess/ you actually want /path/to/release_build/llvm-profdata because > the profiles are generated from binaries compiled with the release build, > so it's the release build

I need to build libLLVM (individual static libraries are fine at the moment) using mingw-w64 cross compilers, i686-w64-mingw32-gcc and (separately) x86_64-w64-mingw32-gcc. I'd like this to work from both Linux and Cygwin build environments. With autotools, this worked fine: ../configure --host=i686-w64-mingw32 and that's it (with mingw32-gcc-c++ installed on Fedora 23, also works fine on