search for: cdavis5x

On Jul 4, 2013, at 10:22 PM, 罗勇刚(Yonggang Luo) wrote: > > 在 2013-7-4 下午8:53，"Charles Davis" <cdavis5x at gmail.com>写道： > > > > > > On Jul 4, 2013, at 1:43 AM, 罗勇刚(Yonggang Luo) wrote: > > > > > LLVM is a modularized software system, so I hope it's was modularized, > > > And ELF.h is definitely belongs to Object by classification, > > > The t...

On May 22, 2013, at 5:33 PM, Charles Davis <cdavis5x at gmail.com> wrote: > In particular, CMake is not distributed with Xcode. ... couldn't because he couldn't get ninja and CMake installed on his workstation. I'm not sure where you got the "cmake isn't included in xcode, therefore noone can use it on an apple platform&qu...

On Thu, Jul 4, 2013 at 10:21 PM, Charles Davis <cdavis5x at gmail.com> wrote: > > On Jul 4, 2013, at 10:22 PM, 罗勇刚(Yonggang Luo) wrote: > > > 在 2013-7-4 下午8:53，"Charles Davis" <cdavis5x at gmail.com>写道： > > > > > > On Jul 4, 2013, at 1:43 AM, 罗勇刚(Yonggang Luo) wrote: > > > > > LLVM is a...

On May 22, 2013, at 10:41 PM, Chris Lattner wrote: > On May 22, 2013, at 5:33 PM, Charles Davis <cdavis5x at gmail.com> wrote: >> In particular, CMake is not distributed with Xcode. ... couldn't because he couldn't get ninja and CMake installed on his workstation. > > I'm not sure where you got the "cmake isn't included in xcode, therefore noone can use it on an app...

On Jul 4, 2013, at 1:43 AM, 罗勇刚(Yonggang Luo) wrote: > LLVM is a modularized software system, so I hope it's was modularized, > And ELF.h is definitely belongs to Object by classification, > The things that confused me is the ELF.h was placed under Support and > don't know why. Because it's also used by the MC layer's direct object emission support. Chip

在 2013-7-4 下午8:53，"Charles Davis" <cdavis5x at gmail.com>写道： > > > On Jul 4, 2013, at 1:43 AM, 罗勇刚(Yonggang Luo) wrote: > > > LLVM is a modularized software system, so I hope it's was modularized, > > And ELF.h is definitely belongs to Object by classification, > > The things that confused me is the ELF.h...

On Wed, May 22, 2013 at 8:33 PM, Charles Davis <cdavis5x at gmail.com> wrote: > > On May 22, 2013, at 5:14 PM, Eric Christopher wrote: > > > Hi All, > > > > Can anyone see good a reason not to move to cmake as our only build > > configuration system and drop future support for autoconf + makefiles > > now that 3...

On May 22, 2013, at 5:14 PM, Eric Christopher wrote: > Hi All, > > Can anyone see good a reason not to move to cmake as our only build > configuration system and drop future support for autoconf + makefiles > now that 3.3 has branched? I can think of several: - When the Clang CMakefiles go to build compiler-rt (if present), they use the compiler used to build Clang and not the

On Jul 24, 2013, at 14:18, Charles Davis <cdavis5x at gmail.com> wrote: > > On Jul 24, 2013, at 11:11 AM, Jeremy Huddleston Sequoia wrote: > >> I recently took a stab at changing the MacPorts llvm-3.4 port from the configure-based build system to the cmake-based build system. >> >> There are a couple of issues that...

On Aug 8, 2013, at 3:04 AM, David Chisnall wrote: > The correct code for this should be (I believe): > > _toglobal: ## @toglobal > ## BB#0: > pushq %rbp > movq %rsp, %rbp > lea %gs:(%rdi), %rax > popq %rbp > ret This won't have the effect you're hoping for. LEA stands for "Load Effective Address"; it only operates on

...er list/stop it sending email? ---------- Forwarded message ---------- From: <llvm.buildmaster at lab.llvm.org> Date: Thu, Sep 17, 2015 at 11:48 PM Subject: buildbot failure in LLVM on clang-cmake-aarch64-full To: Alexei Starovoitov <alexei.starovoitov at gmail.com>, Charles Davis < cdavis5x at gmail.com>, David Blaikie <dblaikie at gmail.com>, David Majnemer < david.majnemer at gmail.com>, Davide Italiano <davide at freebsd.org>, Douglas Katzman <dougk at google.com>, Joerg Sonnenberger <joerg at bec.de>, Matthias Braun <matze at braunis.de>, &qu...

...lorado School of Mines studying in Computer Science. I am a Senior by year and credits, and I am set to graduate in December of 2011. In addition, I have contributed to several open-source projects, including Wine and LLVM. 6. Contact information - E-mail: cdavis at mymail.mines.edu - IRC nick: cdavis5x Chip

On Jul 24, 2013, at 11:11 AM, Jeremy Huddleston Sequoia wrote: > I recently took a stab at changing the MacPorts llvm-3.4 port from the configure-based build system to the cmake-based build system. > > There are a couple of issues that I still haven't been able to work out yet and would like to know if these are just configuration issues on my side or bugs I should file at

...rk on TableGen backend to generate MachineInstr->SDAG tables. Week 6-8: Work on support for custom MachineInstr->SDAG transformation. Week 9-12: Work on SDAG->LLVM IR transformation. Contact Information: email: cdavis (at) mymail (dot) mines (dot) edu phone: (seven-one-nine) 963-4781 IRC: cdavis5x at oftc, cdavis5x at freenode Interest: Since Apple gutted PowerPC support from Mac OS 10.7, I have been searching for a way to run old PowerPC apps. While it would be easy to make my own recompiler manually using LLVM's JIT, I believe it would be far more useful to create a general framework...

On Apr 5, 2013, at 9:19 PM, Jonathan wrote: > I got the following compile error. Did the message-arrays.m can be compiled into .bc? Or need include something for Object C language compile. Those are warnings, not errors. They otherwise compiled just fine. You should have a bitcode file named '1.ll' from each of those commands. Chip > > Jonathan > >

I got the following compile error. Did the message-arrays.m can be compiled into .bc? Or need include something for Object C language compile. Jonathan 118-165-76-229:CodeGenObjC Jonathan$ pwd /Users/Jonathan/llvm/release/src/tools/clang/test/CodeGenObjC 118-165-76-229:CodeGenObjC Jonathan$ clang -emit-llvm -o 1.ll -c message-arrays.m message-arrays.m:5:3: warning: instance method

I recently took a stab at changing the MacPorts llvm-3.4 port from the configure-based build system to the cmake-based build system. There are a couple of issues that I still haven't been able to work out yet and would like to know if these are just configuration issues on my side or bugs I should file at bugs.llvm.org: 1) libclang_rt It looks like the cmake build is missing some runtime

Charles Davis <cdavis5x at gmail.com> writes: > Huh? Intel CC supports the MSVC++ ABI. Zortech (Digital Mars) supports > it, too (though the guy who wrote it isn't too proud of that fact--or > the fact that he even wrote that compiler to begin with). Heck, even > CodeWarrior supported it (as Howard Hin...

...puter > Science. I am a Senior by year and credits, and I am set to graduate in > December of 2011. In addition, I have contributed to several open-source > projects, including Wine and LLVM. > > 6. Contact information > > - E-mail: cdavis at mymail.mines.edu > - IRC nick: cdavis5x > > Chip > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > -- Thanks, Justin Holewinski -------------- next part -------------- An...

....1 and find the trunk has a VA commit from Davis which is not included in the 3.7.1 release. So, I guess I need to directly build the latest trunk instead of the 3.7.1 release. (why 3.7.1 release doesn’t include this patch?) commit 7e96f0f6fffbdebfdac238ae76cc3a791acfa23e Author: Charles Davis <cdavis5x at gmail.com> Date: Tue Aug 25 23:27:41 2015 +0000 Make variable argument intrinsics behave correctly in a Win64 CC function. Summary: This change makes the variable argument intrinsics, `llvm.va_start` and `llvm.va_copy`, and the `va_arg` instruction behave as they do on Win...