search for: yonggang

...ecting 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 > 收件人： yiqiuping1986 > 抄送： > 主题： Re: [LLVMdev] Summer of Code idea -- detecting undefined behavior > > 我没有找到工作，很杯具。 > 2010/3/26, yiqiuping1986 <yiqiuping1986 at 126.com>: >> 没有呢，我还有几年毕业！你应该已经签了吧，呵呵！去哪儿啦！ >> >> >> 2...

...r 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 Support library should be more pure. And >> should not contains >> too much LLVM-related APIs and defines, >> -- >> 此致 >> 礼 >> 罗勇刚 >> Yours >> sincerely...

Hi, I intend to participate in Google's Summer of Code this year, so I'd like to bounce another idea around to see what you guys think. (I posted a similar message to cfe-dev just now.) Be warned: this will shock you. It may even horrify you. 1. Implement a 16-bit x86 backend. (*Chris recoils in horror*) Yeah, I know 16-bit x86 is dead, but I find it interesting for historical purposes

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 directory. > > 2013/6/29 Eric Christopher <echristo at gmail.com>: >> Where would you li...

...> It's my position that a CentOS 6.0-6.x release binary for clang newer than > 3.4.2 is not possible unless CentOS team backports libstdc++4.7 release to > that CentOS release. I'd be happy to learn I'm wrong about that claim BTW. > > On Tue, Jun 28, 2016 at 1:13 PM, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com> > wrote: > >> Hell, Brian, I found a way to install Gcc 5.3 on CentOS 6 without the >> need to building it from source. You may try it on CentOS 6.0 >> That's makes clang/llvm won't depends on the newer version of glibc 2.14 >...

>From my point of view, the Support library should be more pure. And should not contains too much LLVM-related APIs and defines, -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo

...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 29, 2016 at 3:47 AM, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com> wrote: > Well, is that possible to include libstdc++4.7 into llvm? > > On Wed, Jun 29, 2016 at 2:26 AM, Brian Cain <brian.cain at gmail.com> wrote: > >> Sorry if I was unclear, I have no problems building clang against a newer >>...

...;t understand this problem, I have built clang on Windows with > the CMake generated project files without a problem. In fact, it is > even part of our buildbot. > > Can you explain more about what exactly the problem is? > > - Daniel > > On Wed, Aug 5, 2009 at 8:04 AM, 罗勇刚(Yonggang Luo)<luoyonggang at gmail.com> > wrote: >> It's because of lib/Target/*/TargetInfo/CMakeLists.txt (* is Alpha, >> ARM and so on); >> the current line is include_directories( >> ${CMAKE_CURRENT_BINARY_DIR}/.. ${CMAKE_CURRENT_SOURCE_DIR}/.. ) >> and so msvc...

2013/10/19 Rafael Espíndola <rafael.espindola at gmail.com>: > On 19 October 2013 06:01, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com> wrote: >> I found that access llvm-mc from clang driver is impossible, and I >> want to use llvm-mc to compile assembly files, how to do that? > > Try "clang -integrated-as -c test.s" Thank you very much, I use the following command...

-- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161115/80fd3c17/attachment.html>

...CLO baseurl=http://mirror.centos.org/centos/6/sclo/x86_64/rh/ gpgcheck=0 enabled=1 ``` Installation step: ``` yum clean all yum list echo y | yum install devtoolset-4 ``` On Wed, Jun 29, 2016 at 1:15 AM, Brian Cain <brian.cain at gmail.com> wrote: > On Tue, Jun 28, 2016 at 11:50 AM, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com > > wrote: > >> So CentOS before 6.7 is not an option after all? >> Is that possible to use clang on CentOS 6.6 and before? >> >> > Not with these binaries, unless you can update your libc/libstdc++. In > the general sense --...

...lt 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 if I'd have made the package name include > "centos6.7". > > On Tue, Jun 28, 2016 at 11:43 AM, 罗勇刚(Yonggang Luo) < > llvm-dev at lists.llvm.org> wrote: > >> [root at localhost clang+llvm-3.8.0-linux-x86_64-centos6]# cd bin >> [root at localhost bin]# ./clang >> ./clang: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by >> ./clang) >> ./clang: /lib...

...: version `GLIBCXX_3.4.18' not found (required by ./clang) ./clang: /usr/lib64/libstdc++.so.6: version `CXXABI_1.3.5' not found (required by ./clang) ./clang: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by ./clang) -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160629/30513778/attachment.html>

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 isn't handling mingw correctly. On Sat, Oct 19, 2013 at 7:58 AM, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com>wrote: > 2013/10/19 Rafael Espíndola <rafael.espindola at gmail.com>: > > On 19 October 2013 06:01, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com> > wrote: > >> I found that access llvm-mc from clang driver is impossible, and I &g...

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 Support library should be more pure. And > should not contains > too much LLVM-related APIs and defines, > -- > 此致 > 礼 > 罗勇刚 > Yours > sincerely, > Yonggang Luo > > ___________...

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 link options that resident in link.txt is >> /usr/b...

...n easily catch up the support with linux. After we add wasi support in llvm-lic, we can easily get a usable llvm-libc across different platform such as linux/windows/macos/android. don't know if iOS is a target, but these target are very much enough -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200924/5959d313/attachment.html>

...a runtime dependency. It's my position that a CentOS 6.0-6.x release binary for clang newer than 3.4.2 is not possible unless CentOS team backports libstdc++4.7 release to that CentOS release. I'd be happy to learn I'm wrong about that claim BTW. On Tue, Jun 28, 2016 at 1:13 PM, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com> wrote: > Hell, Brian, I found a way to install Gcc 5.3 on CentOS 6 without the need > to building it from source. You may try it on CentOS 6.0 > That's makes clang/llvm won't depends on the newer version of glibc 2.14 > The instruction: &gt...

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 if I'd have made the package name include "centos6.7". On Tue, Jun 28, 2016 at 11:43 AM, 罗勇刚(Yonggang Luo) <llvm-dev at lists.llvm.org > wrote: > [root at localhost clang+llvm-3.8.0-linux-x86_64-centos6]# cd bin > [root at localhost bin]# ./clang > ./clang: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by > ./clang) > ./clang: /lib64/libc.so.6: version `GLIBC_...

...0i32( i32* <ptr>, i32 <delta> ) declare i64 @llvm.atomic.load.umin.i64..p0i64( i64* <ptr>, i64 <delta> ) Why in the llvm function name, some functions containing "..", but others only contains only "." Thanks. -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo