similar to: [LLVMdev] SAFECode Source Code Released

Displaying 20 results from an estimated 5000 matches similar to: "[LLVMdev] SAFECode Source Code Released"

2010 Mar 10
1
[LLVMdev] SAFECode and Poolalloc Branches for LLVM 2.6
Please create a similar branch for Klee; I've been working on porting that to 2.7 as well.<br /> <br /> Best, Erich Ocean<br /> <br /> On Fri, Mar 5, 2010 at 8:43 PM, John Criswell (criswell@uiuc.edu) wrote:<br /> > <br /> > Dear SAFECoders and LLVMers,<br /> > <br /> > There is some new work on moving DSA to the new LLVM 2.7 API.
2009 Aug 17
2
[LLVMdev] Code Freeze this Friday!!!
LLVMers, The 2.6 code freeze is this friday, August 21, at 9pm PDT. All major changes should be checked into SVN at this time. Please monitor the buildbots closely for any failures. I ask you to be very cautious with what you commit to svn over the next few days. This is not the time to be adding experimental code :) Please help us keep LLVM as stable as possible over the next few days.
2010 Mar 06
0
[LLVMdev] How do I download the "poolalloc" module ?
On Mar 6, 2010, at 7:26 AM, Patrick Sathyanathan wrote: > Hi, > > I'm interested in using the "Data Structure Analysis" that is apparently in the "poolalloc" module according to the documentation on alias analysis in LLVM. I have downloaded and built LLVM 2.6 on MinGW but the sources do not seem to include anything related to pool allocation. I don't think
2009 Aug 18
0
[LLVMdev] Code Freeze this Friday!!!
Good day Tanya, I would just like to clarify this for myself and a few other people who maybe wondering, Does this code freeze apply to; * Clang. * Compiler-RT. Thanks for your time, Best Regards, Edward O'Callaghan. 2009/8/17 Tanya Lattner <lattner at apple.com>: > LLVMers, > > The 2.6 code freeze is this friday, August 21, at 9pm PDT. > > All major changes should
2009 Sep 23
2
[LLVMdev] [llvm-commits] [PATCH] BlocksRuntime updates for Linux
No, As it worked fine before. I can't see the #if that goes with +#elif defined(__WIN32__) as you removed -#if TARGET_OS_MAC. Please go over your #if / #endif blocks and trail the #endif with a comment. I am willing to bet there is a problem there. Thanks for your time, Edward. 2009/9/23 Shantonu Sen <ssen at apple.com>: > Sounds like your system compiler doesn't support
2009 Nov 12
1
[LLVMdev] Google's Go
On Nov 12, 2009, at 10:25 AM, Edward O'Callaghan wrote: > No, its up to them which backend they want to use. > Sounds like they think that GCC is super quick compared to LLVM. Looks > like another fud fart out of google to me. Edward, this is no place for comments like this. Evan > > 2009/11/12 Jon McLachlan <mclachlan at apple.com>: >> Any plans to make LLVM
2009 Sep 14
3
[LLVMdev] FYI: Phoronix GCC vs. LLVM-GCC benchmarks
screw that site, its useless info run by a linux gnu zealot. 2009/9/14 Chris Lattner <clattner at apple.com>: > On Sep 14, 2009, at 3:20 AM, Stefano Delli Ponti wrote: > >> http://www.phoronix.com/scan.php? >> page=article&item=apple_llvm_gcc&num=1 > > Unfortunately, they don't specify what flags are used, what > architecture is compiled for etc.
2016 Feb 05
2
Why do we have a git tag called "release_35@215010"?
I.e., I see this when I run `git fetch`: ``` $ git fetch -v llvm.org From http://llvm.org/git/llvm = [up to date] master -> llvm.org/master = [up to date] release_1 -> llvm.org/release_1 = [up to date] release_16 -> llvm.org/release_16 = [up to date] release_20 -> llvm.org/release_20 = [up to date] release_21 -> llvm.org/release_21 = [up to date]
2010 Mar 08
3
[LLVMdev] How do I download the "poolalloc" module ?
Bob Wilson wrote: > On Mar 6, 2010, at 7:26 AM, Patrick Sathyanathan wrote: > > >> Hi, >> >> I'm interested in using the "Data Structure Analysis" that is apparently in the "poolalloc" module according to the documentation on alias analysis in LLVM. I have downloaded and built LLVM 2.6 on MinGW but the sources do not seem to include anything
2009 Sep 23
0
[LLVMdev] [llvm-commits] [PATCH] BlocksRuntime updates for Linux
Seems pretty clear cut to me. #if defined(HAVE_OSATOMIC_COMPARE_AND_SWAP_INT) && defined (HAVE_OSATOMIC_COMPARE_AND_SWAP_LONG) ... #elif defined(__WIN32__) ... #elif defined(HAVE_SYNC_BOOL_COMPARE_AND_SWAP_INT) && defined (HAVE_SYNC_BOOL_COMPARE_AND_SWAP_LONG) ... #else #error unknown atomic compare-and-swap primitive #endif The problem isn't mismatched #if/#endif. The
2009 Sep 23
2
[LLVMdev] [llvm-commits] [PATCH] BlocksRuntime updates for Linux
Clang does indeed built it with one warning. [ 55%] Building C object lib/CMakeFiles/CompilerRT-Common.dir/gcc_personality_v0.c.o /export/home/edward/lab/llvm/build/compiler-rt/lib/gcc_personality_v0.c:232:36: warning: implicit declaration of function '__builtin_eh_return_data_regno' is invalid in C99 [-Wimplicit-function-declaration] _Unwind_SetGR(context,
2009 Nov 12
2
[LLVMdev] Google's Go
Any plans to make LLVM work with Google's new language, Go? http://www.technewsworld.com/story/Go-Go-Google-Programming-Language-68622.html?wlc=1257974768&wlc=1258041607&wlc=1258047741
2016 Feb 05
2
Why do we have a git tag called "release_35@215010"?
> On 2016-Feb-05, at 15:22, James Y Knight <jyknight at google.com> wrote: > > That usually happens when someone deletes and then recreates an svn branch with the same name, as happened in r215001 and r215011. > It can be deleted now, if anyone wants to. ``` $ git push llvm.org :release_35 at 215010 fatal: unable to access 'http://llvm.org/git/llvm.git/': The requested
2009 Sep 23
2
[LLVMdev] [llvm-commits] [PATCH] BlocksRuntime updates for Linux
Breaks Builds on Solaris and AuroraUX with: bash-3.2$ make Scanning dependencies of target BlocksRuntime [ 1%] Building C object BlocksRuntime/CMakeFiles/BlocksRuntime.dir/runtime.c.o /export/home/edward/lab/llvm/build/compiler-rt/BlocksRuntime/runtime.c:77:2: error: #error unknown atomic compare-and-swap primitive /export/home/edward/lab/llvm/build/compiler-rt/BlocksRuntime/runtime.c: In
2009 Sep 15
2
[LLVMdev] Status of blocks runtime in compiler-rt?
Hi folks, So, various folks are in the process of porting Grand Central Dispatch to FreeBSD (c.f. http://libdispatch.macosforge.org and http://lists.macosforge.org/pipermail/libdispatch-dev for mailing list discussion on the topic) and are making good progress, but one of the issues they're running into is support for Blocks in FreeBSD. On the one hand, they could try and back-port
2010 Mar 09
1
[LLVMdev] Changed: Build errors for poolalloc using MinGW/gcc 4.4.0
Thanks Bob and John for the response. I am having problems building poolalloc with my MinGW and gcc 4.4.0 setup. Running make in the poolalloc directory results in a bunch of "undefined reference to ..." link errors building Release/lib/LLVMDataStructure.dll. I looked at the command line for this link and found that there are no libraries included with "-l..." options even
2009 Sep 23
0
[LLVMdev] [llvm-commits] [PATCH] BlocksRuntime updates for Linux
Sounds like your system compiler doesn't support gcc-style builtin atomics. Please use a different compiler? Shantonu Sent from my MacBook On Sep 22, 2009, at 7:54 PM, Edward O'Callaghan wrote: > Breaks Builds on Solaris and AuroraUX with: > > bash-3.2$ make > Scanning dependencies of target BlocksRuntime > [ 1%] Building C object
2009 Nov 12
0
[LLVMdev] Google's Go
No, its up to them which backend they want to use. Sounds like they think that GCC is super quick compared to LLVM. Looks like another fud fart out of google to me. 2009/11/12 Jon McLachlan <mclachlan at apple.com>: > Any plans to make LLVM work with Google's new language, Go? > >
2009 Nov 10
7
[LLVMdev] Hello!
I'm interested in contributing to LLVM, but I'm a rather bad C/C++ developer. I do most of my work in Ada and was wondering if there was a way to still contribute to something other than the Ada frontend.
2011 Oct 06
0
[LLVMdev] svnsync of llvm tree
Oliver Schneider <gmane at assarbad.net> writes: >>> However, we have official git mirrors of most of the projects on >>> llvm.org, would using them instead of svnsync be an option for you? >> >> Well, if the authoritative source code control system for all the >> llvm projects is svn, I'd just as soon use svn as the tool at my end. > The git