similar to: [LLVMdev] Top Level Stuff

Displaying 20 results from an estimated 100000 matches similar to: "[LLVMdev] Top Level Stuff"

2007 Jul 02
0
[LLVMdev] Top Level Stuff
> The current SVN repository has several modules at the top level (llvm, > test-suite, java, stacker, etc.). The modules contain the software that > makes up the LLVM Project. However, there is nothing at the top level > that explains any of this. So, I am considering doing the following at > the top level of the repository (i.e. in > http://llvm.org/svn/llvm-project): > >
2007 Jun 30
0
[LLVMdev] Top Level Stuff
I just have a couple of comments on this: 1. Minor issue: I think the README should be in text format (or text and HTML) so that someone checking it out on the command line can read it easily. 2. If the projects directory goes away, we should provide a different mechanism for someone starting a new project based on LLVM to use as a template. This could include, minimally, a Makefile and
2007 Jul 02
1
[LLVMdev] Top Level Stuff
Hi Tanya, On Sun, 2007-07-01 at 19:38 -0700, Tanya M. Lattner wrote: > > The current SVN repository has several modules at the top level (llvm, > > test-suite, java, stacker, etc.). The modules contain the software that > > makes up the LLVM Project. However, there is nothing at the top level > > that explains any of this. So, I am considering doing the following at >
2007 Jun 30
6
[LLVMdev] Repository Layout
All, I'm finding the current layout a bit frustrating, not to mention that it breaks all the documentation. We currently have modules laid out like this: llvm/trunk/... llvm/branches/... llvm/tags/... stacker/trunk/... stacker/branches/... stacker/tags/... and similarly for all the other modules (test-suite, java, poolalloc, etc.). Unfortunately, this "standard"
2007 Jul 02
2
[LLVMdev] Top Level Stuff
On Sun, 1 Jul 2007, Tanya M. Lattner wrote: > I don't think we should have a docs module. Its much better to allow a > person to check out only llvm and get the appropriate documentation. Same > for hlvm, and whatever project. Its very inconvenient to check out > multiple things just to get llvm and docs. To put it another way, I think the docs for the subproject should follow
2009 Jun 24
2
[LLVMdev] Garbage collection implementation
Jon Harrop wrote: > The simplest way is surely to reuse HLVM because it provides everything you > need and is even written in the right language! ;-) Is there a web page with HLVM docs? There's a README.txt in the subversion repository: https://llvm.org/svn/llvm-project/hlvm/trunk/README.txt which says: HLVM comes with documentation in HTML format. These are provided in
2018 Nov 16
6
New LLVM git repository conversion prototype
Hi James, I've started working with the prototype layout in context of Google's internal infrastructure. With deep apologies, I have a (very late, I know) pair of requests that have only recently solidified for me. 1. Could you add annotated tags after the cut point of each release? (I think this would probably be easy.) 2. Could you mark branch/tag operations somehow other than a
2018 Nov 15
2
New LLVM git repository conversion prototype
On 10/11/2018 03:27 PM, James Y Knight via llvm-dev wrote: > TLDR: https://github.com/llvm-git-prototype/ exists as a read-only mirror of SVN, and is being updated continuously with a script running on an llvm-project AWS VM. > Hi James, What is the current status of the monorepo, have you resolved all the known issues with the history? Are there any other changes that need to be made
2007 Jul 03
3
[LLVMdev] Top Level Stuff
On Mon, 2 Jul 2007, Reid Spencer wrote: >>> it can be created in the repository, making the checkout process a simple, >>> transparent 'svn co'. This is entirely complementary to your idea. >> >> Yes, but that checks everything out, which is badness. > > Not really. He didn't define "./". If "./" is: >
2007 Jul 01
0
[LLVMdev] Repository Layout
On 2007-06-30, at 18:36, Reid Spencer wrote: > I'm finding the current layout a bit frustrating, not to mention > that it breaks all the documentation. [...] I would rather see it > laid out like this: > > trunk/llvm/... > trunk/stacker/... > trunk/java/... > > branches/llvm/... > branches/stacker/... > branches/java/... > >
2007 Jul 01
1
[LLVMdev] Repository Layout
Hi Gordon, On Sun, 2007-07-01 at 08:22 -0400, Gordon Henriksen wrote: > On 2007-06-30, at 18:36, Reid Spencer wrote: > > > > I'm finding the current layout a bit frustrating, not to mention > > that it breaks all the documentation. [...] I would rather see it > > laid out like this: > > > > > > > > > trunk/llvm/... > >
2007 Mar 28
2
[LLVMdev] x86 in win32 folder
I don't want to drive this too off topic, but I should be clear that I wasn't suggesting that the LLVM project adopt XPJ as it's official config file format for Visual Studio. I have found it useful to use XPJ to generate the initial VS projects for a code base that doesn't already have VS projects. I also find it nice to be able to see all of the config options in a
2018 Nov 17
2
New LLVM git repository conversion prototype
On Fri, Nov 16, 2018 at 4:04 PM NAKAMURA Takumi <geek4civic at gmail.com> wrote: > Hello, David. > > On Sat, Nov 17, 2018 at 7:46 AM David Jones via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi James, >> >> I've started working with the prototype layout in context of Google's >> internal infrastructure. With deep apologies, I
2007 Mar 28
0
[LLVMdev] x86 in win32 folder
On Wed, 2007-03-28 at 10:22 -0500, Christopher Lamb wrote: > I don't want to drive this too off topic, but I should be clear that I > wasn't suggesting that the LLVM project adopt XPJ as it's official > config file format for Visual Studio. I have found it useful to use > XPJ to generate the initial VS projects for a code base that doesn't > already have VS projects.
2004 Oct 07
2
[LLVMdev] RE: MinGW Tablegen
Hi As requested from Paolo, I've sent him the tablegen tool. The tool is able to compile the td files (given in the makefile) on windows without any complaints. Henrik >From: Paolo Invernizzi <arathorn at fastwebnet.it> >Date: Thu, 7 Oct 2004 14:27:11 +0200 > >Hi Henrik, > >As you may remember, I'm trying to use the LLVM core tools under Visual >Studio.
2006 May 15
4
Anyone got a copy of File_Column trunk
Anyone able to post a copy of the svn trunk of file_column? The website''s been down for the past few days, and I''ve only got the last release (0.31, I think), which is missing a whole load of goodies. Tx
2006 Feb 08
2
How to install RailsCron?
Hi, I would like to start running a background procedure once a user logs in to his account on the website. For this I am considering using the RailsCron object. However, I am not able to download it. I am new to Rails. Can someone give me the excat command I should use to get RailsCron? Can someone suggest a better way of running a procedure in the background? Thanks -Yash -- Posted via
2006 Jun 16
5
[slightly OT] Problem with subversion 1.3.1 on OSX Tiger
I have a subversion repo on a Debian Sarge server. I do rails development on two Debian workstations (home, work) and also a MacBookPro. I installed subversion from Darwinports. Things worked ok for a while and I did commits from and updates to all three machines until today. When I did svn status I noticed a lock on the working dir. $ svn status ? Rakefile ? readme ! L . .... etc I cannot
2004 Oct 22
6
[LLVMdev] Makefile.rules Changes / automake update (IMPORTANT!)
Hello, I've closed PR106 (use automake) as WONTFIX. I've already delineated the problems with automake in previous posts but as of now, all the automake related stuff has been removed from the repository. In an effort to start making our makefile system better, I've committed changes to Makefile.rules and a few library Makefiles that nearly double the speed of our compilations. I
2007 Aug 16
2
[LLVMdev] rantings about llvm-top
Hi Raid ! I used llvm-top at home and in the company and I basically I like it. Here are some comments: - the README.txt says that all routines use a common library and therefore accept a common set of arguments. But this is confusing, because things like VERBOSE look like an environment variable. Somehow people are used that arguments are always starting with - and that they are