search for: compilefarm

Another suggestion I've been given is this: http://gcc.gnu.org/wiki/CompileFarm. You wouldn't even have to supply hardware. On 17 September 2010 17:13, Daniel Berlin <dberlin at dberlin.org> wrote: > Can't offer it in the bay area, but i can offer space in oregon state > university (which is where the osuosl machines reside). > http://osuosl.org/service...

On 09/19/2010 03:48 PM, Ben Laurie wrote: > Another suggestion I've been given is this: > http://gcc.gnu.org/wiki/CompileFarm. You wouldn't even have to supply > hardware. The compile farm is a set of machines that is shared between different users. They are great to try your code on different architectures, but the level of control is a lot lower than the level you get from dedicated machines. So it is probabl...

...ryone has a ARM machine to help ARM testing. That's why > Mehmet mentioned Debian has resource. Sorry but the goal of Debian porterboxes is not for upstream testing their software but for packaging purposes. You should instead have a look to the GCC compilation farm: http://gcc.gnu.org/wiki/CompileFarm Some LLVM developers are using these servers for testing LLVM and Dragonegg. Sylvestre

...his? I will ask if we can have a machine to run a polly perf build-bot. > Thank you. That would be great if we can find a sponsor. > Otherwise, I think I have to run all test on my laptop. > An alternative is to set up an automatic tester in the gcc compile farm http://gcc.gnu.org/wiki/CompileFarm and run the perf measurements on several different machines: collect all the data and use a noise filter to discard any hiccups due to the use of the system by another process, etc. http://repo.or.cz/w/gcc-perf-regression-tester.git/blob_plain/HEAD:/analyze.R http://repo.or.cz/w/gcc-perf-regressi...

...ing others would be important, so that we have a fully featured nightly tester .And finally all the php scripts need to be updated according to the required new features. Thanks in advance. Please add your comments.! Regards, -Rajika [1] - http://llvm.org/nightlytest/ [2] - http://gcc.gnu.org/wiki/CompileFarm -- gautamabuddha - http://www.gautamabuddha.org/ comp.lang.c - http://groups.google.com/group/comp.lang.c/topics -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080405/53a41e79/attachment.html>

Hi Tanya, I got the go-ahead from Laurent Guerby for using the gcc compile farm for running the llvm nightly tester (http://gcc.gnu.org/wiki/CompileFarm). I will try to set this up, but in fact anyone can apply for a login as described at the above webpage. Ciao, Duncan. PS: The machines are all running linux and are mostly amd64 or x86-32, but there is also an alpha.

...n 24 April 2013 12:01, Sylvestre Ledru <sylvestre at debian.org> wrote: > Sorry but the goal of Debian porterboxes is not for upstream testing > their software but for packaging purposes. > > You should instead have a look to the GCC compilation farm: > http://gcc.gnu.org/wiki/CompileFarm > Some LLVM developers are using these servers for testing LLVM and > Dragonegg. > Hi Folks, I'm separating some of our boards for release testing. What kind of hardware do you need and how many of each? I'm not promising anything, but I already have a Beagle and a Panda just for...

...ave a fully featured nightly > tester .And finally all the php scripts need to be updated according > to the required new features. > Thanks in advance. Please add your comments.! > Regards, > -Rajika > > [1] - http://llvm.org/nightlytest/ > [2] - http://gcc.gnu.org/wiki/CompileFarm > > -- > gautamabuddha - http://www.gautamabuddha.org/ > comp.lang.c - http://groups.google.com/group/comp.lang.c/topics > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists....

On Thursday 20 November 2008 16:59, Tanya M. Lattner wrote: > > It's all in the proposal I posted a week or so ago. > > Yes, your proposal said that the community must agree on the set of tests > used to validate it. You haven't said what the conclusion was. Also, in True enough. My assumption is we'll figure that out soon. I'll post a separate thread to start

On 24/04/2013 12:21, 陳韋任 (Wei-Ren Chen) wrote: > Hi Mehmet, > > Thanks for the info. I just contacted DSA (Debian System Admin, I > guess), and he said we have to prepare information list on [1] and > ask DD to approve it. Are you a DD, or Sylvestre is? I am (cf my email address). Why would like to do in this context ? Thanks, Sylvestre

Hi Sylvestre, > > Thanks for the info. I just contacted DSA (Debian System Admin, I > > guess), and he said we have to prepare information list on [1] and > > ask DD to approve it. Are you a DD, or Sylvestre is? > I am (cf my email address). > Why would like to do in this context ? Well, not everyone has a ARM machine to help ARM testing. That's why Mehmet

Hi Everyone, I'm working on GCC112, which is POWER System S822 (Power8) machine running CentOS 7 machine (https://gcc.gnu.org/wiki/CompileFarm): $ cat /etc/centos-release CentOS Linux release 7.3.1611 (AltArch) I'm trying to determine L1 data cache size. When the following code runs it returns 0. The man pages state -1 is an error, so I think its claiming to succeed. cacheLineSize = sysconf(_SC_LEVEL1_DCACHE_LINESIZE);...

...that we have a fully featured nightly tester .And finally all > the php scripts need to be updated according to the required new features. > Thanks in advance. Please add your comments.! > Regards, > -Rajika > > [1] - http://llvm.org/nightlytest/ > [2] - http://gcc.gnu.org/wiki/CompileFarm > >

Hi Renato, > > Sorry but the goal of Debian porterboxes is not for upstream testing > > their software but for packaging purposes. > > > > You should instead have a look to the GCC compilation farm: > > http://gcc.gnu.org/wiki/CompileFarm > > Some LLVM developers are using these servers for testing LLVM and > > Dragonegg. > > > > Hi Folks, > > I'm separating some of our boards for release testing. What kind of > hardware do you need and how many of each? I'm not promising anything, but >...

All, We are in desperate need of linux x86 testers (32 or 64 bit). If you could set one up, the LLVM project would be very grateful. Right now we have virtually no testers covering this platform. Directions to set up a tester are here: http://llvm.org/docs/TestingGuide.html#nightly These directions could be improved of course. If you have any questions, I will be happy to assist you in

Can't offer it in the bay area, but i can offer space in oregon state university (which is where the osuosl machines reside). http://osuosl.org/services Why do you need access if you have people willing to handle support tickets and remote console/power control cards? I have yet to see a problem that i could not solve (since the cards can display console, control power to the machine, etc)

Hi all, I don't have very high hopes, but does anyone happen to have available some kind of colocation services in the Bay Area that they could donate to LLVM? I would really like to establish a proper LLVM lab somewhere instead of relying on hardware which is residing at various companies. I would be willing to personally donate some hardware, but don't have any place to put it. My

On Mon, 28 Sep 2020 at 10:37, John Paul Adrian Glaubitz < glaubitz at physik.fu-berlin.de> wrote: > So, I think in case there was a problem with the backend in LLVM, the > community > would have enough momentum to work towards solving this issue. > Great! I agree. But we will enable the target in Debian the moment it becomes > usable > and we will expose it to as much

Dear Tobias and all LLVM/Polly developers, Thank you very much for all your help and advice. I have submitted my proposal to GSoC 2013 application system: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/star/1. Some tables and paragraphs are simplified to make it more readable on GSoC official pages. Any suggestion or comment would be appreciated. At 2013-05-03

On 05/03/2013 11:39 AM, Star Tan wrote: > Dear Tobias, > > > Thank you very much for your very helpful advice. > > > Yes, -debug-pass and -time-passes are two very useful and powerful > options when evaluating the compile-time of each compiler pass. They > are exactly what I need! With these options, I can step into details > of the compile-time overhead of each pass.