similar to: [LLVMdev] Getting Started Doc Bugs

2012/6/16 Justin Holewinski <justin.holewinski at gmail.com>: > Under Python installation, you mention that Python is only needed for the > test suite.  This is not true, as the normal LLVM build still requires > Python. That's right. Now, python>=2.4 is essential. (In contrast, perl is not required, IIRC) > I would seriously consider splitting this up into

On Sat, Jun 16, 2012 at 3:29 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi Takumi, > > THANK YOU for your excellent review! It makes all the work worthwhile in > itself. > > It is getting "late" here (it is early morning) so I am about to call it a > day. But I will contemplate and incorporate your suggestions tomorrow, and > send you a full

Dear Chandler, First, can you articulate why you want to move the test suite to Github? Is it taking up too much space, or is there some other problem that you're trying to solve? I think you clearly explain why moving the revision history isn't necessary, but it's not clear to me what problem you are trying to solve. Second, if we move the revision history to Github, it would

Óscar Fuentes <ofv at wanadoo.es> writes: > Are you saying that git-svn is slow at pulling changes? It is quite okay > in my experience, unless you pull once every other month. But I can't > relate that to your original assertion quoted above. I can't use git-svn to pull because we use svn on our end. One can't do this: (Upstream) svn <--> git-svn <-->

Dave, > Either the directory should be named llvm-test or the top-level configure.ac > should be changed to recognize "test-suite." Thanks. Fixed in r37852 -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Eric Christopher <echristo at apple.com> writes: > On Nov 8, 2011, at 7:20 PM, David A. Greene wrote: > > I couldn't figure out how to run the test-suite. Are there up-to-date > instructions somewhere? llvm-gcc doesn't exist anymore... > > Easiest is to check out the test-suite branch into projects and then after you configure and build from the top

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

Renato Golin <rengolin at gmail.com> writes: > On Thu, 17 Oct 2019 at 18:10, David Greene <greened at obbligato.org> wrote: >> From other discussion, it sounds like at least some people are open to >> asm tests under clang. I think that should be fine. But there are >> probably other kinds of end-to-end tests that should not live under >> clang. > >

All, 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): 1. /README.html Just a short

Renato Golin <rengolin at gmail.com> writes: > On Wed, 16 Oct 2019 at 21:00, David Greene <greened at obbligato.org> wrote: >> Can you elaborate? I'm talking about very small tests targeted to >> generate a specific instruction or small number of instructions. >> Vectorization isn't the best example. Something like verifying FMA >> generation is a

My biggest concerns and care-abouts are largely what Matthias expressed below. Most of them have been addressed already further down the thread. I hope that the move to github in practice would mean that the only difference is that I 'git clone https://github...' instead of 'git clone http://llvm.org/git/test-suite.git' ? Thanks, Kristof On 24/02/2016 22:25, Matthias Braun

Hi Takumi, THANK YOU for your excellent review! It makes all the work worthwhile in itself. It is getting "late" here (it is early morning) so I am about to call it a day. But I will contemplate and incorporate your suggestions tomorrow, and send you a full reply. I think I originally wrote a document where I addressed both Visual Studio and MinGW, but then decided that there were

On 2008-04-20, at 21:05, Terence Parr wrote: > On Apr 20, 2008, at 5:36 PM, Gordon Henriksen wrote: > >> Since the semispace heap doesn't actually work (it's an example, at >> best), I suggest you simply copy the stack visitor into your >> project; it's only a dozen lines of code or so. > > > Ok, copying; can't find ShadowStackEntry though.

greened at obbligato.org (David A. Greene) writes: > I can't use git-svn to pull because we use svn on our end. One can't do > this: > > (Upstream) svn <--> git-svn <--> git <--> git-svn <--> svn (Downstream) > > because the revisions in the two svn repositories don't have anything to > do with each other. That's what you deserve, for

I'm looking at creating an llvm repository similar to clang-tests, but containing a more recent version of the GDB (& possibly other, but I'm mostly interested in debug info testing at the moment) test suite. This code is licensed (among other things, it seems) under GPLv3 which may be something that needs to be highlighted. With all that in mind: is this reasonable? If so, what

Yes, I would hope that for most this boils down to cloning a different URL. Except for folks pushing patches to the test suite, I'm moderately confident there would be no other difference. It's the pushing patches side that would need to be sorted out in more detail. On Thu, Feb 25, 2016 at 12:48 AM Kristof Beyls <kristof.beyls at arm.com> wrote: > My biggest concerns and

> 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): > >

Hi, I have several times over the past three months tried to retrieve the trunk version of LLVM/Clang/Compiler-RT from Subversion and then tried to build it on Windows: Without success. Also, I occasionally get emails from people who ask me why LLVM/Windows does not build (they find my name in the mailing list archive). This has made me ponder the issue and I came up with the following scheme

Not a big deal, but the "<http://xiph.org/svn.html>Subversion Access" link on http://www.speex.org/download.html page should probably point to: http://www.xiph.org/svn/ rather than: http://xiph.org/svn.html Tom ______________________________________________ Tom Harper Lead Software Engineer SightSpeed - <http://www.sightspeed.com/>http://www.sightspeed.com/ 918 Parker

Hi, I'm planning to upgrade an old public/internal development infrastructure and will use CentOS 5.4 x86_64 as basis. One of the critical server is Subversion (as an Apache httpd module). We currently use Subversion v1.4 on the server and v1.6 on our clients. While I was very happy with the v1.4 server over the years, we now sometimes have weird issues which seem related to compatibility