search for: vector_llvm

Hi, As advertised to some, I've checked in a BETA VERSION of my vector extensions to LLVM. It is checked in as a CVS branch off of the main line. You can get the branch by doing a normal llvm checkout and adding the argument -r vector_llvm. E.g., to check out from anonymous CVS, you would do this: • cvs -d :pserver:anon at llvm-cvs.cs.uiuc.edu:/var/cvs/llvm login • Hit the return key when prompted for the password. • cvs -z3 -d :pserver:anon at llvm-cvs.cs.uiuc.edu:/var/cvs/llvm co -r vector_llvm llvm This will produce a f...

...is the lockdown of the root repository directory. I tried something like this but it breaks due to the restrictions: git svn init --stdlayout https://<user>@llvm.org/svn/llvm-project/llvm \ --ignore-paths="^.*(Apple|PowerPC.*|SVA|eh-experimental|ggreif|non-call-eh|parallel|release_.*|vector_llvm|wendling|May2007|checker|cremebrulee|start|RELEASE_1.*|RELEASE_2[0-7])" Obviously, replace <user> with whatever it needs to be to allow dcommit to work. Ideally we'd have clang and llvm-gcc git mirrors as well via the --prefix argument to git-svn init, but let's not get ahead o...

...arset="windows-1252" > > Hi, > > As advertised to some, I've checked in a BETA VERSION of my vector > extensions to LLVM. It is checked in as a CVS branch off of the main > line. You can get the branch by doing a normal llvm checkout and > adding the argument -r vector_llvm. E.g., to check out from anonymous > CVS, you would do this: > > • cvs -d :pserver:anon at llvm-cvs.cs.uiuc.edu:/var/cvs/llvm login > • Hit the return key when prompted for the password. > • cvs -z3 -d :pserver:anon at llvm-cvs.cs.uiuc.edu:/...

Matthieu, On Tue, Mar 1, 2011 at 8:02 AM, Matthieu Moy <Matthieu.Moy at grenoble-inp.fr> wrote: > At some point in the past, an anti-git-svn system had been set up on > llvm.org. Has this been disabled since? I don't manage to do much with > git-svn: Maybe sure. Anton said it is disabled to access upper directories with svn. Thus, we (accessing llvm.org remotely) cannot do

...the trouble with branches is the lockdown of the root repository > directory. Surely not (at the server) > git svn init --stdlayout https://<user>@llvm.org/svn/llvm-project/llvm \ >  --ignore-paths="^.*(Apple|PowerPC.*|SVA|eh-experimental|ggreif|non-call-eh|parallel|release_.*|vector_llvm|wendling|May2007|checker|cremebrulee|start|RELEASE_1.*|RELEASE_2[0-7])" Several problems here: 1. Bunch of additional branches / tags are created due to multiple branch points. I don't recall for llvm, but for clang we'll end with two tags per each release. Something like: $ git branch...

...of you who have write access to the LLVM CVS repository, I need to ask you to take more care when moving or renaming files. If done improperly, moving files can cause headaches when doing updates from the repository or merging revisions between branches (which is becoming more common with the vector_llvm branch). There are two ways that you can move a CVS file: 1) Use the CVS commands: a) cd into your working directory. Move the file from the old location to the new location. b) Use cvs rm to remove the file from its old location. c) Use cvs add to add the file to its new location. d) Use c...

...write access to the LLVM CVS repository, I > need to ask you to take more care when moving or renaming files. If > done improperly, moving files can cause headaches when doing updates > from the repository or merging revisions between branches (which is > becoming more common with the vector_llvm branch). > > There are two ways that you can move a CVS file: > > 1) Use the CVS commands: > > a) cd into your working directory. Move the file from the old location > to the new location. > > b) Use cvs rm to remove the file from its old location. > > c) Use cvs a...

...s to the LLVM CVS repository, I >>need to ask you to take more care when moving or renaming files. If >>done improperly, moving files can cause headaches when doing updates >>from the repository or merging revisions between branches (which is >>becoming more common with the vector_llvm branch). >> >>There are two ways that you can move a CVS file: >> >>1) Use the CVS commands: >> >>a) cd into your working directory. Move the file from the old location >>to the new location. >> >>b) Use cvs rm to remove the file from its old l...

...ches is the lockdown of the root repository >> directory. > Surely not (at the server) > >> git svn init --stdlayout https://<user>@llvm.org/svn/llvm-project/llvm \ >> --ignore-paths="^.*(Apple|PowerPC.*|SVA|eh-experimental|ggreif|non-call-eh|parallel|release_.*|vector_llvm|wendling|May2007|checker|cremebrulee|start|RELEASE_1.*|RELEASE_2[0-7])" > Several problems here: > 1. Bunch of additional branches / tags are created due to multiple > branch points. I don't recall for llvm, but for clang we'll end with > two tags per each release. Somethin...

All, We are considering removing some branches and tags in the conversion process from CVS to SVN. We don't want to do this in a vaccuum, so please read carefully. A deficiency in the cvs2svn script causes it to bloat the Subversion repository (significantly, as in 10x) in the conversion of branches and tags. We can minimize the impact of this by only keeping branches and tags that we really

...s to the LLVM CVS repository, I >>need to ask you to take more care when moving or renaming files. If >>done improperly, moving files can cause headaches when doing updates >>from the repository or merging revisions between branches (which is >>becoming more common with the vector_llvm branch). >> >>There are two ways that you can move a CVS file: >> >>1) Use the CVS commands: >> >>a) cd into your working directory. Move the file from the old location >>to the new location. >> >>b) Use cvs rm to remove the file from its old l...