similar to: [LLVMdev] [cfe-dev] Cross-compiling with clang

I know pc-lint is working fine on detecting some nasty coding fault. But is it illegal implement it in clang? And also there is so much other tools for code analyze:) 2010/3/26, yiqiuping1986 <yiqiuping1986 at 126.com>: > 呵呵，不急，还有一学期的时间。 > > > 2010-03-26 > > > > yiqiuping1986 > > > > 发件人： 罗勇刚(Yonggang Luo) > 发送时间： 2010-03-26 15:05:33 > 收件人：

I means visual studio c++ 2008, do you build clang+llvm with .sln files, and these files are generated by cmake? I do of that. And because vs c++ can't recognize path such a:/filepath/.. Properlyn it's recognized as a:/filepath So we need change /.. to /../ or /../. 2009/8/6, Daniel Dunbar <daniel at zuster.org>: > I don't understand this problem, I have built clang on

Its seems an bug in langref, is there anyone have an look or give an explain? 2010/5/5, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com>: > declare i8 @llvm.atomic.load.max.i8.p0i8( i8* <ptr>, i8 <delta> ) > declare i16 @llvm.atomic.load.max.i16.p0i16( i16* <ptr>, i16 <delta> ) > declare i32 @llvm.atomic.load.max.i32.p0i32( i32* <ptr>, i32

Now I can convert llvm and clang to mercurial with full history, especially for clang, the current git mirror for clang is not tracking the whole history(for those revisions under cfe/cfe/trunk), but the one I converted is good on this, I was using an own modified hgsubversion to do this, but I got problems on converting hg to git. 2011/8/19, FlyLanguage <flylanguage at gmail.com>:

On Oct 5, 2009, at 3:17 PM, 罗勇刚(Yonggang Luo) wrote: > Is there anyone get the time to apply this patch? I've committed my suggested fix. There's no point in setting the LINKER_LANGUAGE property of every LLVM library, because CMake figures out the right language based on the file extensions of the source files. - Doug > 2009/10/2, Douglas Gregor <dgregor at apple.com>:

Mmm, do you see that patch? Because the order of those linked library is incorrect. Mingw can't generate libCindex.dll. So I midified the likage order. Also, for the reason of removing duplicated code, I removed some unnecessay cmake code. And add an new cmake function 2009/10/7, Douglas Gregor <dgregor at apple.com>: > > On Oct 7, 2009, at 8:36 AM, 罗勇刚(Yonggang Luo) wrote: >

Is there anyone get the time to apply this patch? 2009/10/2, Douglas Gregor <dgregor at apple.com>: > > On Oct 1, 2009, at 6:36 AM, 罗勇刚(Yonggang Luo) wrote: > >> At the first glance, it's coming with that c-index-test is just >> only containing c files (without cpp(cxx,c++) files). >> >> So cmake recognize it as pure C project, >> and so it's

Is it possible to merger mingw32 and mingw64 with mingw, because we can distinguish them with arch(i386,amd64) 2009/8/15, Anton Korobeynikov <anton at korobeynikov.info>: > Hello > >> I add solaris and pic16. >> And add support for mingw. > Mingw part is not ok. The proper rules should be: > > i[[3456789]]86-*-mingw32* => mingw32 > x86_64-*-mingw* =>

We know if we add -emit-llvm option to llvm-gcc will deduce emit bc code, but the problem once llvm-gcc as the linker in some configure system, it's will call the default ld in default and have no idea to change this, maybe we can set the default linker as llvm-ld once -emit-llvm as the option of gcc. And we can't just rename llvm-ld as ld because. llvm-ld will call binutils ld. So we

I have a question. If the size of long is 8 on your x64 platform. Because the size of long is so different on different platform, sad it is. 2009/9/23, David Greene <dag at cray.com>: > How are bitfields handled in StructLayout? In LLVM 2.5 the > struct is unambiguously size by: > > StructSize += TD.getTypePaddedSize(Ty); // Consume space for this data > > In LLVM 2.6

Wow, I also meet this error before, I'll be pleasure if anyone can solve this problem, and by the way, are you using msys as the building env? It's seems that mingw/cmake is working but mingw/msys, and I didn't ever try with mingw/cygwin:) thanks. 2009/10/1, Ronald Pijnacker <pijnacker at dse.nl>: > Hi all, > > When I try to build llvm on windows/mingw32, I get the

Did pecoff support means we can linkage llvm generated obj files to msvc's obj files? 2010/1/22, Jim Crafton <jim.crafton at gmail.com>: >> Nope, llvm's .s output is only compatible with GAS and other at&t syntax >> assemblers.  It turns out that MASM syntax is highly ambiguous and MASM is >> not production quality for use by a compiler.  This is why visual

Going to be interesting layering issues if you do the latter. Then you have CodeGen depending upon DebugInfo instead of just a header in Support. -eric On Fri, Jun 28, 2013 at 11:08 AM, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com> wrote: > For example, > ELF.h MachO.h and COFF.h > should moved into Object directory with new name. > and Dwarf.h should moved into DebugInfo

I have one thing not clear to me. If the llvm diect generate object code. Then how about the llvm assembler processing llvm code with inline assembly? Indeed, it's seems now llvm is direct using gas syntax in the assembly code. And because it's generate .S files, so it can be manipulated by binutils. But there is one day, no binutils any further, how to deal with these inline assembly.

For example, ELF.h MachO.h and COFF.h should moved into Object directory with new name. and Dwarf.h should moved into DebugInfo directory. 2013/6/29 Eric Christopher <echristo at gmail.com>: > Where would you like to move them? > > -eric > > On Fri, Jun 28, 2013 at 10:38 AM, 罗勇刚(Yonggang Luo) > <luoyonggang at gmail.com> wrote: >> From my point of view, the

I don't know if hg is a possible choice for llvm-project. Because we can using hgsubversion interactive with subversion. That's means we need only an svn server. and create an hg minor. And we can push to and pull from the subversion server. ---------- Forwarded message ---------- From: 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com> Date: 2010/3/4 Subject: I can't find the

declare i8 @llvm.atomic.load.max.i8.p0i8( i8* <ptr>, i8 <delta> ) declare i16 @llvm.atomic.load.max.i16.p0i16( i16* <ptr>, i16 <delta> ) declare i32 @llvm.atomic.load.max.i32.p0i32( i32* <ptr>, i32 <delta> ) declare i64 @llvm.atomic.load.max.i64.p0i64( i64* <ptr>, i64 <delta> ) declare i8 @llvm.atomic.load.min.i8.p0i8( i8* <ptr>, i8

So CentOS before 6.7 is not an option after all? Is that possible to use clang on CentOS 6.6 and before? On Wed, Jun 29, 2016 at 12:48 AM, Brian Cain <brian.cain at gmail.com> wrote: > Yes, I believe it was built against centos 6.7. I wanted to build it > against an older release but couldn't quite bootstrap it without newer > libstdc++. > > Sorry, it would be clearer

It is possible to statically link against libstdc++, yes. I don't quite know all the pieces to the recipe in order to get that to work. It would require changes to the release script in order to get those configuration changes all the way through the third phase build. I don't believe any other tarball release does this, so it would at least be an unconventional release. On Wed, Jun

Ah, so clang only understands the spelling mingw32, not mingw. That'll give you COFF. :) On Mon, Oct 21, 2013 at 11:23 AM, Reid Kleckner <rnk at google.com> wrote: > I can confirm I get the same behavior, and that's a real bug. If you use > --target=i686-pc-win32, you get COFF, and that should be a good workaround > for now. There must be a conditional somewhere that