similar to: [LLVMdev] test-suite

Displaying 20 results from an estimated 30000 matches similar to: "[LLVMdev] test-suite"

2010 Oct 17
0
[LLVMdev] test-suite
On 10/17/10 3:28 PM, Kenneth Uildriks wrote: > Does test-suite work with clang, or do I still need llvm-gcc? It works with Clang. The buildbots run it with clang all the time. Chip
2011 Nov 25
2
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
In the case I posted I had removed that line, however, you still get the __3F_ in the generated assembly with it. Sent from my iPhone On Nov 25, 2011, at 2:15 PM, Charles Davis <cdavis at mymail.mines.edu> wrote: > > On Nov 25, 2011, at 8:39 AM, Michael Spencer wrote: > >> So I was taking a look at Microsoft C++ ABI support while on vacation, >> and ran into a major
2011 Mar 29
3
[LLVMdev] [GSoC] "Microsoft Direct3D shader bytecode backend" proposal
Here's the other of my proposals for this year's Google Summer of Code. (The first is on cfe-dev.) It was suggested to me by Dan Kegel (from the Wine project, they really want this). Title: Microsoft Direct3D shader bytecode backend Abstract: There is a distinct lack of open-source frameworks for compiling HLSL, the shader language used by Direct3D, into bytecode that D3D can
2011 Nov 25
0
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
On Nov 25, 2011, at 2:22 PM, bigcheesegs at gmail.com wrote: > In the case I posted I had removed that line, however, you still get the __3F_ in the generated assembly with it. Huh. It only seems to happen with a Windows triple or a Linux triple. Doesn't happen with a Mac triple, though--probably because the Darwin assembler supports quoted symbols (i.e. you can enclose an identifier in
2010 Apr 07
1
[LLVMdev] SoC 2010 Proposal
Here's my SoC 2010 proposal. I submitted it a long time ago (last week, to be precise), but didn't post it to the list. You can review it here: http://socghop.appspot.com/gsoc/student_proposal/show/google/gsoc2010/cdavis/t127000394358 Chip
2012 Jun 21
2
[LLVMdev] [cfe-dev] is configure+make dead yet?
On Jun 20, 2012, at 6:19 PM, Chandler Carruth wrote: > On Wed, Jun 20, 2012 at 5:13 PM, Nick Lewycky <nlewycky at google.com> wrote: > Is there anybody who is certain that our autoconf dependency needs to stay around? Are there developers stuck on systems that don't have a recent enough cmake in their most recent release, or maybe are using some features from configure+make that
2011 Mar 29
2
[LLVMdev] [GSoC] "Microsoft Direct3D shader bytecode backend" proposal
On 3/29/11 5:14 AM, Justin Holewinski wrote: > On Mon, Mar 28, 2011 at 9:22 PM, Charles Davis <cdavis at mymail.mines.edu > <mailto:cdavis at mymail.mines.edu>> wrote: > > Here's the other of my proposals for this year's Google Summer of Code. > (The first is on cfe-dev.) It was suggested to me by Dan Kegel (from the > Wine project, they really
2011 Mar 29
0
[LLVMdev] [GSoC] "Microsoft Direct3D shader bytecode backend" proposal
On Mon, Mar 28, 2011 at 9:22 PM, Charles Davis <cdavis at mymail.mines.edu>wrote: > Here's the other of my proposals for this year's Google Summer of Code. > (The first is on cfe-dev.) It was suggested to me by Dan Kegel (from the > Wine project, they really want this). > > Title: Microsoft Direct3D shader bytecode backend > > Abstract: > > There is a
2010 Oct 26
2
[LLVMdev] Implementing the hotpatch attribute for X86
Hi, According to http://blogs.msdn.com/b/freik/archive/2006/03/07/x64-hotpatchability.aspx, 'hotpatchable' functions on x86 (and by extension, x86-64) are preceded by six bytes of padding and start with a two byte instruction. The problem is that, still being relatively unfamiliar with the x86 backend, I have no idea how to implement this for the 'hotpatch' attribute I just added.
2011 May 17
2
[LLVMdev] How are system calls made?
How do you do this in LLVM? open: push dword mode push dword flags push dword path mov eax, 5 push eax ; Or any other dword int 80h add esp, byte 16 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110516/a61fe83b/attachment.html>
2010 Jul 12
13
16-Bit/DOS Suppor Missing?
Currently attempting to run an old PC game on my Mac (Leopard). I've installed Wine using MacPorts, which worked flawlessly. Now when I attempt to install my PC Game the terminal responds with "16-Bit/DOS Support missing." Is there a way to fix this?
2011 Jun 02
3
[LLVMdev] Advice on MachineMoves and SEH
On Jun 2, 2011, at 9:11 AM, Jim Grosbach wrote: > > On Jun 2, 2011, at 6:20 AM, Rafael Ávila de Espíndola wrote: > >> On 11-06-02 6:56 AM, Anton Korobeynikov wrote: >>> Hi Chip, >>> >>>> Because of all this, it's hard to reconstruct the SEH information from >>>> the MachineMove array. I have thought about adding a new array specific
2010 Apr 16
1
[LLVMdev] Generating incorrect bitcode file
On 4/16/10 12:17 AM, Nick Lewycky wrote: > Pranav Garg wrote: >> Hi, >> >> I am generating the .bc file using the following command >> >> $ llvm-gcc -emit-llvm -S -o pointer.bc ../../../test/pointer.c >> >> But when I run any pass using opt it gives the following error : >> $ ./opt -basicaa pointer.bc >> ./opt: Bitcode stream should be a
2010 Oct 26
2
[LLVMdev] Implementing the hotpatch attribute for X86
On 10/26/10 5:24 PM, Michael Spencer wrote: > The linker adds the padding. Also, the first instruction just has to > be two bytes or longer. Not exactly two bytes. How then does the linker know to add the padding? I assume there's a PE-COFF attribute that will do that, but what about other file formats, like ELF or Mach-O? Bear in mind that I'm doing this for the Wine project, so
2011 May 13
1
[LLVMdev] Difficulty compiling LLVM-based tools with clang
On 5/12/11 7:08 PM, Rafael Ávila de Espíndola wrote: > The problem comes from SearchForAddressOfSpecialSymbol.cpp: > > // FIXME: Currently disabled when using Clang, as we don't always > have our > // runtime support libraries available. > #ifndef __clang__ > #ifdef __i386__ > EXPLICIT_SYMBOL(__eprintf); > #endif > #endif > > Now, exactly
2011 May 17
0
[LLVMdev] How are system calls made?
On 5/16/11 10:30 PM, Hans Stimer wrote: > How do you do this in LLVM? > > open: > push dword mode > push dword flags > push dword path > mov eax, 5 > push eax ; Or any other dword > int 80h > add esp, byte 16 Same as in C: either with inline assembly, or by calling syscall(2). Chip
2011 Jun 04
0
[LLVMdev] Compiling whole programs to bitcode
On 6/3/11 10:43 PM, Russell Wallace wrote: > On Sat, Jun 4, 2011 at 5:39 AM, Nick Lewycky <nicholas at mxc.ca> wrote: >> If a program uses a templated function from a C++ library, either the C++ >> library provides an implementation of the template instantiated to that >> type, or else the whole implementation was available in the header and ends >> up in the TU of
2011 Jun 04
2
[LLVMdev] Compiling whole programs to bitcode
On Sat, Jun 4, 2011 at 5:39 AM, Nick Lewycky <nicholas at mxc.ca> wrote: > If a program uses a templated function from a C++ library, either the C++ > library provides an implementation of the template instantiated to that > type, or else the whole implementation was available in the header and ends > up in the TU of the program, not the library ((or else you'd get a link
2011 Jun 04
2
[LLVMdev] Compiling whole programs to bitcode
With Clang, it's reasonably straightforward to compile a C/C++ file to bitcode. Is there a way to compile a program together with all the standard library functions it uses, to that format? That is, suppose you have hello.c that calls printf, how would you go about generating the bitcode representation of both the main function from hello.c, and printf itself (plus whatever other standard
2009 Oct 06
3
[LLVMdev] Some additions to the C bindings
My front-end is sync'd with the trunk now, and working well, but it required some additional functions exposed in the C bindings. I hereby submit them for review and approval for inclusion in the trunk. -------------- next part -------------- A non-text attachment was scrubbed... Name: cbindings.patch Type: application/octet-stream Size: 7269 bytes Desc: not available URL: