similar to: [LLVMdev] PDB debug info

Displaying 20 results from an estimated 900 matches similar to: "[LLVMdev] PDB debug info"

2012 Sep 12
0
[LLVMdev] PDB debug info
Oops, I've managed to exclude the list... On 12 September 2012 19:28, Nathan Jeffords <blunted2night at gmail.com> wrote: > > > On Wed, Sep 12, 2012 at 8:50 AM, Manu <turkeyman at gmail.com> wrote: > >> On 12 September 2012 18:19, Nathan Jeffords <blunted2night at gmail.com>wrote: >> >>> This project seems to have some ability to convert to
2012 Sep 12
2
[LLVMdev] PDB debug info
On Wed, Sep 12, 2012 at 9:46 AM, Manu <turkeyman at gmail.com> wrote: > Oops, I've managed to exclude the list... > > > On 12 September 2012 19:28, Nathan Jeffords <blunted2night at gmail.com>wrote: > >> >> >> On Wed, Sep 12, 2012 at 8:50 AM, Manu <turkeyman at gmail.com> wrote: >> >>> On 12 September 2012 18:19, Nathan
2012 Sep 12
1
[LLVMdev] PDB debug info
On Wed, Sep 12, 2012 at 12:19 PM, Manu <turkeyman at gmail.com> wrote: > On 12 September 2012 20:49, Nathan Jeffords <blunted2night at gmail.com>wrote: > >> >> On Wed, Sep 12, 2012 at 9:46 AM, Manu <turkeyman at gmail.com> wrote: >> >>> /Z7, that's the one. Maybe this approach can be used by LLVM? I presume >>> LLVM is capable of
2012 Sep 12
0
[LLVMdev] PDB debug info
On 12 September 2012 20:49, Nathan Jeffords <blunted2night at gmail.com> wrote: > > On Wed, Sep 12, 2012 at 9:46 AM, Manu <turkeyman at gmail.com> wrote: > >> /Z7, that's the one. Maybe this approach can be used by LLVM? I presume >> LLVM is capable of producing CV info already? Maybe this configuration is >> already possible? >> It'd be
2012 Sep 12
2
[LLVMdev] State of Win64 exceptions?
Hi again, Can anyone tell me about the state of Win64 exceptions? I've noticed that there are a good few related patches since the release of 3.1. Is it working now? Is it likely 3.2 will support Win64 exceptions? Cheers. - Manu -------------- next part -------------- An HTML attachment was scrubbed... URL:
2014 Dec 19
2
[LLVMdev] [Patches][RFC] What to do about bitcode streaming.
Hi Rafael, Would you mind waiting for Derek to come back from vacation to discuss this? We do use this code and could improve how it's used and tested within LLVM. Derek is the best person to discuss this, he'll be back in mid-January. Thanks, JF On Fri, Dec 19, 2014 at 6:41 AM, Rafael EspĂ­ndola < rafael.espindola at gmail.com> wrote: > > > I CC'ed llvmdev to put a
2012 Sep 17
0
[LLVMdev] State of Win64 exceptions?
Nobody? Is this basically dead? Won't happen? In progress? :/ On 12 September 2012 18:53, Manu <turkeyman at gmail.com> wrote: > Hi again, > > Can anyone tell me about the state of Win64 exceptions? > I've noticed that there are a good few related patches since the release > of 3.1. Is it working now? > Is it likely 3.2 will support Win64 exceptions? > >
2008 Sep 04
3
OT: workstation recommends: Thinkmate?
I'm looking to buy a new workstation, and it looks like Thinkmate makes what I need -- their vsx "virtually silent" variety. I hestitate because I wasn't happy with a laptop I bought a few years ago from a small outfit that sold Linux boxes exclusively. Does anyone have experience with Thinkmate, and in particular, the VSX line? If the later, is it really quiet. I run Centos
2013 Jul 30
5
[LLVMdev] PNaCl Bitcode reference manual
Hello, Following an earlier email ( http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-June/063010.html), we've published an initial version of the PNaCl bitcode reference manual online - http://www.chromium.org/nativeclient/pnacl/bitcode-abi. The PNaCl bitcode is a restricted subset of LLVM IR. The reference manual is quite terse, so for the bigger picture I'll repost links to the design
2013 Jun 19
3
[LLVMdev] Building a stable bitcode format for PNaCl - based on LLVM IR
> From the provided documentation I understood that in memory data > structures of a PNaCl program are incompatible to the host program because > ABIs are different (e.g. PNaCl pointers are always 32-bit even when running > on x86_64 platform). > So PNaCl program can't access any data structures of the host program > directly. The only communication way is by using syscalls,
2013 Jun 19
0
[LLVMdev] Building a stable bitcode format for PNaCl - based on LLVM IR
Am 19.06.2013 18:01, schrieb JF Bastien: > > From the provided documentation I understood that in memory data > structures of a PNaCl program are incompatible to the host program > because ABIs are different (e.g. PNaCl pointers are always 32-bit > even when running on x86_64 platform). > So PNaCl program can't access any data structures of the host >
2012 Dec 04
5
[LLVMdev] Proposal: Adding aligned instruction bundle support to MC
Hello, We (the Portable Native Client team) would like to start upstreaming our LLVM modifications which contain support for Software Fault Isolation (SFI) as required for sandboxing programs to run under Native Client. Since the "total patch size" is quite big, we are splitting the effort to manageable chunks that can be committed, tested and reviewed separately as independently as
2013 Jun 18
6
[LLVMdev] Building a stable bitcode format for PNaCl - based on LLVM IR
Hello, [The first paragraph is safe to skip if you already know what PNaCl is.] The Portable Native Client (PNaCl) project is a toolchain for producing portable bitcode from C and C++ code and running in securely and efficiently on the web via Native Client. For more details see this presentation from the last Google I/O: https://developers.google.com/events/io/sessions/325679543and
2020 Apr 19
3
State of NaCl in monorepo?
Hi all, LLVM/Clang supports an OS called 'NaCl' (llvm/include/llvm/ADT/Triple.h). It apparently hasn't had any development since 2015. This page https://developer.chrome.com/native-client/migration mentions that NaCl is deprecated. Is it still used? If not, I would propose that we remove it. I created a patch https://reviews.llvm.org/D78441 which I think can delete 90% of the
2009 Feb 02
2
Trunk with Polocom Video Conferencing Unit
I was wondering if anyone can help me with a problem we have at one of our sites. We have setup a Asterisk Trunk to a Avaya PBX, ie ... Avaya <-> Asterisk (1.2.30) <-> External ISDN Network BUT They also have a Polycom VSX 7000 that with some sort of BRI converters that plugs into the Avaya. The Trunk is working well except for Video Conference Calls. The Polocom can receive
2015 Jul 04
4
[LLVMdev] LLVM parsers for popular languages? - Python, Rust, Go
Thanks, happy to of confirmed. With that in mind, will use the AST modules provided by the languages (with the exception of libclang for C++). Antoine: Am aware of Numba, nice job there BTW. So is there a [decoupled] LLVM parser which I can use to read Python files and analyse objects (including computing their attributes in OO and setattr scenarios)? On Wed, Jul 1, 2015 at 10:23 PM, Antoine
2011 Jun 01
2
[LLVMdev] Fw: Thinking about "whacky" backends
Sorry, forgot to CC the list. ----- Forwarded Message ----- > From: Samuel Crow <samuraileumas at yahoo.com> > To: Joachim Durchholz <jo at durchholz.org> > Cc: > Sent: Tuesday, May 31, 2011 9:35 PM > Subject: Re: [LLVMdev] Thinking about "whacky" backends > > Hello, > > > ----- Original Message ----- >> From: Joachim Durchholz
2009 Jun 05
0
[LLVMdev] How to stop symbol searching without aborting
Marcus Zetterquist <marcus.zetterquist at gmail.com> writes: > Today we use Lua to let 3rd party developers add driver-like modules > to our application. > > The advantages to using Lua compared to DLL:s etc. are that: > > 1) the same driver binary can be used on all OS:es and processor > architectures etc. [snip] > I'm looking into using LLVM and the
2012 Apr 18
2
[LLVMdev] Hi guys and llvmbrains! :P
Hello, Is it possible to use LLVM like JVM (virtual machine)? If so, How? Can this be used to create hardware-independent and OS-independent binaries? Thank you
2011 Jun 01
0
[LLVMdev] Fw: Thinking about "whacky" backends
On May 31, 2011, at 7:36 PM, Samuel Crow wrote: <snip> >> >> Now my idea for a whacky backend: Just a wrapper of the bitcode writer with its >> own special target triple: bitcode-tarrget-neutral and a generic data layout >> that aligns to single bytes as a placeholder only. It should disallow >> overriding the alignment of individual instructions to avoid