search for: release_32

Hello, I have tried a lot fix this error but am not able to can you please find me a solution am trying to compile the SAFECode in Cygwin Environment to work for windows. used make -j4 command to make the files in cygwin i have got this error make[5]: Leaving directory '/home/uidr7475/Work/LLVM_OBJ/projects/safecode/tools/clang/include' /usr/bin/cp: cannot stat

Anton, please add release_32 also in; clang-tools-extra compiler-rt dragonegg libcxxabi lldb They have release_32 in svn. I don't know they might be released, though. And, could you suppress generating refs/heads/svn-tags and prune them for now? I am sure that orphan branches will stress the llvm.org server to begin git...

Should be there On Fri, Nov 16, 2012 at 3:00 PM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > Anton, please add release_32 also in; > > clang-tools-extra > compiler-rt > dragonegg > libcxxabi > lldb > > They have release_32 in svn. I don't know they might be released, though. > > And, could you suppress generating refs/heads/svn-tags and prune them for now? > I am sure that orphan b...

...inding down, and that means release notes! There are two pieces to this. First, if you're an external LLVM user, we'd like to list you as such in the release notes. This is a great way to get some free advertisement. The section is here: http://llvm.org/viewvc/llvm-project/llvm/branches/release_32/docs/ReleaseNotes.html?revision=HEAD#externalproj Please email a blurb to include to Pawel. Also, note that being listed in the 3.1 release notes *does not* mean that you will automatically be listed in 3.2. The section will soon be cleared out. Next, if you're an llvm contributor, please...

> I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. Unfortunately, this requires manual grafting, since git-svn does really bad job here. I'm going to work on this tonight. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg Sta...

Should be there. Please let me know if there are any problems with them On Wed, Nov 14, 2012 at 9:19 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. > Unfortunately, this requires manual grafting, since git-svn does > really bad job here. > > I'm going to work on this tonight. > > -- > With best regards, Anton Korobeynikov > Faculty of Mathemati...

...int that part of SMACK got deprecated, but now I would like to revisit it since it was working quite well. Therefore, I would like to learn what's the status of the poolalloc project, and in particular its DSA analysis. I've seen there are regular commits, and also there is a branch called release_32, which is I presume following LLVM's 3.2 release. If that about right? Basically, I would appreciate if somebody would comment if I can count on DSA being supported and following LLVM releases in the future. Thanks a lot! -- Zvonimir

...poolalloc's svn history, this option was removed on (or before) 2011. May I know why this one was removed ? and is there any equivalent option (or options combination) in current poolalloc project ? 2. I checked the svn history of poolalloc. there is no update to trunk since last Nov. the release_32 branch was updated this March. I am wondering which one is good to use ? and are they compatible with latest llvm trunk or llvm release_3_3 branch ? thank you in advance btw: I am not in the llvmdev email alias, please include my email address in your reply. -Jing -------------- next part ------...

...ate] release_27 -> llvm.org/release_27 = [up to date] release_28 -> llvm.org/release_28 = [up to date] release_29 -> llvm.org/release_29 = [up to date] release_30 -> llvm.org/release_30 = [up to date] release_31 -> llvm.org/release_31 = [up to date] release_32 -> llvm.org/release_32 = [up to date] release_33 -> llvm.org/release_33 = [up to date] release_34 -> llvm.org/release_34 = [up to date] release_35 -> llvm.org/release_35 = [up to date] release_35 at 215010 -> llvm.org/release_35 at 215010 = [up to date]...

...ot deprecated, but now I would like > to revisit it since it was working quite well. > > Therefore, I would like to learn what's the status of the poolalloc > project, and in particular its DSA analysis. I've seen there are > regular commits, and also there is a branch called release_32, which > is I presume following LLVM's 3.2 release. If that about right? Correct. The release_32 branch of poolalloc works with the release_32 branch of LLVM (which should be the upcoming LLVM 3.2 to be released soon). For the moment, we're not planning to have poolalloc trunk track...

...vs pass. If you need a shape graph, you can use the DSGraph interface directly. If you could tell me how you want to use DSA, I can explain which approach to use and how to make it work. > > 2. I checked the svn history of poolalloc. there is no update to trunk > since last Nov. the release_32 branch was updated this March. I am > wondering which one is good to use ? and are they compatible with > latest llvm trunk or llvm release_3_3 branch ? The release_32 branch is the actively maintained branch at the moment. When we're ready to to move to LLVM 3.3, we'll merge the...

Dear Pawel and All, Pawel (and other release managers), can you ask the project maintainers for each project whether they want a release branch before creating it next time? Alternatively, can you leave branch creation up to the project maintainers as in the past? Pawel, you created a release_32 branch of SAFECode last night without my consultation. That commit itself is fine since we just happen to be tracking LLVM mainline right now; I'll just tell SAFECode developers to move development to the release_32 branch. However, in general, you can't assume that SAFECode mainline i...

We have branched for the 3.2 release! Some "sticky reminders": You can get all of the 3.2 code from the appropriate .../branches/release_32/ You can track state of the 3.2 release through so called "Umbrella bug" : http://llvm.org/bugs/show_bug.cgi?id=13893 Hopefully it will not "rain bugs" on us and we will not need it that much! After branching all patches require prior approval so please contact respective code...

On 1/11/2013 7:15 AM, Justin Holewinski wrote: > Removed from trunk. Pawel can decide if its necessary to update the > tarballs. > > Thanks for the report! Apparently git-svn does not delete removed > directories. PTX directories still exists in release_32 branch and RELEASE_32/final. But they are all empty so PTX can not be build. > > > On Fri, Jan 11, 2013 at 1:36 AM, 陳韋任 (Wei-Ren Chen) < > chenwj at iis.sinica.edu.tw> wrote: > >> Hi Pawel, >> >> PTX already be replaced with NVPTX. However, PTX subdirect...

...status of this issue? Are there still any > problems in the pass if i compile and run it? > > > I do not believe that the status has changed. I believe the -dsa-aa pass > in DSA is still removed and has not been resurrected (at least not with a > patch that applied cleanly to the release_32 branch). > > If someone wants to resurrect -dsa-aa with a patch that cleanly applies to > the release_32 branch or the trunk branch, I'll review it and apply it. > > Regards, > > John Criswell > > > > Thanks, > > Daniel. > > > __________________...

...; llvm.org/release_27 > = [up to date] release_28 -> llvm.org/release_28 > = [up to date] release_29 -> llvm.org/release_29 > = [up to date] release_30 -> llvm.org/release_30 > = [up to date] release_31 -> llvm.org/release_31 > = [up to date] release_32 -> llvm.org/release_32 > = [up to date] release_33 -> llvm.org/release_33 > = [up to date] release_34 -> llvm.org/release_34 > = [up to date] release_35 -> llvm.org/release_35 > = [up to date] release_35 at 215010 -> llvm.org/release_35 at 215010 &...

...ing LLVM 2.9, so which version of poolalloc I should use ? -------------------------------------------- Qiuping Yi Institute Of Software Chinese Academy of Sciences On Fri, Jan 30, 2015 at 11:12 PM, John Criswell <jtcriswel at gmail.com> wrote: > Dear Qiuping, > > If you use the release_32 branch of poolalloc, then you need to use LLVM > 3.2. > > For directions on compiling poolalloc with LLVM 3.2, please the SAFECode > build directions at http://safecode.cs.illinois.edu/docs/Install.html. > You can just skip the steps in the directions that compile SAFECode. > >...

Hi, all I want to use the alias analysises in project poolalloc, but I encounter some problem during installing it. I install poolalloc as follow: 1) cd llvm/projects svn co http://llvm.org/svn/llvm-project/poolalloc/branches/release_32 poolalloc 3) cd LLVM-object-directory make tools-only cd projects/poolalloc make When I carried out "make", I get the next error information: llvm[2]: Compiling AddressTakenAnalysis.cpp for Release+Asserts build (PIC) AddressTakenAnalysis.cpp:18:30: fatal error: llvm/IR/CallS...

Hi, I'm trying to compile release 3.2 of DragonEgg (checked out from http://llvm.org/svn/llvm-project/dragonegg/branches/release_32. I'm at revision 170458), under Ubuntu (Ubuntu 12.04.1 LTS (GNU/Linux 2.6.39-gcg-20121018 x86_64)) and I get the following error. tmroeder at myubuntu:~/src/dragonegg$ make Compiling utils/TargetInfo.cpp Linking TargetInfo Compiling Aliasing.cpp /root/src/dragonegg/src/Aliasing.cpp:37:23: fata...

Deal all, Recently i am searching for a intra-procedure alias analysis pass and the -ds-aa pass seems to be the one i am looking for. However, i find this post described that the rDSA code in PoorAlloc project was abandoned before ... https://groups.google.com/d/topic/llvm-dev/FMLmIh9Nz84/discussion But some other guys were interested in it and John Criswell also made a request in bug database on