GCC Compile Farm Project

Contents

  1. GCC Compile Farm Project
    1. How to Get Involved ?
    2. User Accounts
    3. Projects Ideas
    4. Currently Running
    5. Current Status
    6. News
    7. History and Sponsors

How to Get Involved ?

If you are a GCC developer and want access to the CompileFarm for GCC development and testing, or if you are a free software developer wishing to set up automated testing of a piece of free software with the current GCC latest release or development version (preferably free software with a test suite), please send

  1. your ssh public key (HOME/.ssh/authorized_keys format) in attachment and not inline in the email and

  2. AND your prefered UNIX login (see below User Accounts for already taken logins)

to laurent at guerby dot net.

Mailing list, SVN for scripts and ticket system are hosted on gna.org:

https://gna.org/projects/gcc-cfarm/

Information and tips on using the farm are given below. Compile Farm user projects should have an entry below. Graphics about the farm load are available here:

http://gcc12.fsffrance.org/munin/

User Accounts

  1. guerby
  2. ian
  3. fxcoudert
  4. olly
  5. spop
  6. manu
  7. mstein
  8. bagnara
  9. hp
  10. jerryd
  11. manuel
  12. geoffk
  13. amylaar
  14. david
  15. rask
  16. pinskia
  17. revitale
  18. tschwinge
  19. segher
  20. baldrick
  21. ebotcazou
  22. henryn
  23. tromey
  24. ghazi
  25. guilt
  26. bozo
  27. joel
  28. younes
  29. kuba
  30. nightstrike
  31. apop
  32. rpeckhoff
  33. ktietz
  34. sam
  35. rwild

Projects Ideas

Currently Running

Port GCC to Intel's 16-bit architecture.

RaskIngemannLambertsen is trying to port GCC to the Intel 8086 CPU family. Nodes gcc01, gcc03, gcc04, gcc07, gcc08 and gcc09 are used for testing patches that could affect existing targets. Tests are run at low priority and use of the nodes is sporadic. The Intel 8086 CPU has both 8-bit registers and 16-bit registers. The work on getting GCC to fully support such CPUs includes:

  1. Fixing the assumption in subreg_get_info() (rtlanal.c) that if a value is stored in multiple hard register, then those hard register all have the same size. To fix that, subreg_get_info() will be rewritten. The targets that are the trickiest to get right are i?86-*-* with -m128bit-long-double and powerpc-unknown-eabispe. Note: This part has been postponed because the new lower-subreg pass reduces the problem and I've worked around the cases that subreg_get_info() can't currently handle.
  2. In reload.c, fixing find_valid_class() and callers having the same problem as subreg_get_info().
  3. Fixing unspecified reload bugs as they turn up.

General bug fixes and enhancements are also tested from time to time.

Maintaining the GNU/Hurd tool chain

ThomasSchwinge is using node gcc12 for working on maintaining the GNU/Hurd tool chain. This means building cross binutils, cross GCC, cross-compiling glibc and suchlike. Working with various versions of the involved programs means using a lot of disk space, however feel free to request a clean up if you need space on the machine's storage.

Automatic bootstrap and regression testing

If you have a GCC Compile Farm account, you can automatically test your GCC patches by copying them to /n/13/spop/patches/ that has the correct rights set. The patch can contain several markers that instruct the tester where to send the results by email, what branch and revision of GCC to use, and the configure and make flags. One can use the prepare_patch.sh script for filling up all this optional information, and for selecting the defaults for each case. The last step before copying the patch to the tester is to gpg sign it.

An example of a patch header for the HEAD version of autovect-branch, configuring only c, c++, and fortran, using vectorization during bootstrap, and only checking the vectorization specific tests: 

email:foo@bar.com
branch:autovect-branch
revision:HEAD
configure:--enable-languages=c,c++,fortran
make:CFLAGS="-g" BOOT_CFLAGS="-O2 -g -msse2 -ftree-vectorize"
check:RUNTESTFLAGS=vect.exp

Autobuilds for coLinux

HenryNe is using node gcc11 for building coLinux from source. It uses cross target mingw32 and runs ons per day with low priority.

CGNU Project

rpeckhoff is documenting the operation of the current gcc build system on nodes gcc11-gcc14. He is using graphviz, Doxygen, and his own scripts to help discover and document source interdependencies. His project's progress is at http://re.mpqx.biz.

All languages testing

LaurentGuerby is running bootstrap and check in loop with languages all,ada on active branches and report to gcc-testresult

Developing the Win64 port of GCC

http://mingw-w64.sf.net/ is committed to creating a viable platform for using gcc on windows natively. We run build and testsuites constantly, and foster development and porting of mainstream applications such as Firefox (http://www.mozilla.org) and VLC (http://www.videolan.org) to the Win64 platform.

your project here

your description here

Current Status

As of 20080415, on all CFARM machines:

Datacenter http://jexiste.fr , static public IP, 100 Mbit/s up/down, debian etch amd64 

name   disk  CPU         Notes
gcc11  580G  2x2x2.0 GHz Opteron 2212 / 4GB RAM / Dell SC1345
gcc12  580G  2x2x2.0 GHz Opteron 2212 / 4GB RAM / Dell SC1345

Datacenter http://www.skyrock.com/ , static public IP, 1000 Mbit/s up/down, debian etch amd64 

gcc13  580G  2x2x2.0 GHz Opteron 2212 / 4GB RAM / Dell SC1345
gcc14  750G  2x4x3.0 GHz Xeon X5450 / 16GB RAM / Dell Poweredge 1950

Datacenter http://www.inria.fr/saclay/ , static public IP , ssh only, debian etch amd64 

gcc15 160G 1x2x2.8 GHz Xeon dual core "paxville" / 1 GB RAM / Dell SC1425
gcc16 580G 2x4x2.2 GHz Opteron 8354 "Barcelona B3" / 16 GB RAM
gcc17 580G 2x4x2.2 GHz Opteron 8354 "Barcelona B3" / 16 GB RAM

Datacenter http://www.macaq.org/ , DSL dynamic IP, 10 Mbit/s down, 1 MBit/s up, ubuntu breezy 5.10 

gcc01  16G   2x1.00 Ghz Pentium 3 / 1 GB RAM / Dell Poweredge 1550 + additional 32 GB disk
gcc02  16G   2x1.00 Ghz Pentium 3 / 1 GB RAM / Dell Poweredge 1550
gcc03  16G   2x1.26 Ghz Pentium 3 / 1 GB RAM / Dell Poweredge 1550
gcc05  16G   2x1.00 Ghz Pentium 3 / 1 GB RAM / Dell Poweredge 1550
gcc06  16G   2x1.00 Ghz Pentium 3 / 1 GB RAM / Dell Poweredge 1550
gcc07  32G   2X1.26 Ghz Pentium 3 / 1 GB RAM / Dell Poweredge 1550
gcc09  32G   2x0.93 Ghz Pentium 3 / 1 GB RAM / Dell Poweredge 1550

Datacenter http://www.guerby.org/ , DSL dynamic IP, 10 Mbit/s down, 1 MBit/s up, debian etch amd64 

gcc04  500G  1x4x2.2 GHz Phenom 9500 / 4GB RAM / home made

Currently offline 

gcc08  32G   2x1.26 Ghz  Pentium 3 / 1 GB RAM / Dell Poweredge 1550

News

History and Sponsors

In August 2005 FSF France received in donation from BNP Paribas 9 Dell poweredge 1550 bi processor 1U machines with one SCSI disk and 1GB RAM, processors total 19.5 GHz distributed as follows:

The machines are about four years old, so of course there may be hardware problems in the coming years, but we might also be able to get cheap parts on the used market (or from other donations).

Hosting for those 9 1U machines is donated by the http://jexiste.org/ staff in a Paris datacenter (provided we maintain low use of external bandwidth).

In June 2007 FSF France purchased 3 Dell SC1345 to replace older Dells that were taken offline in http://jexiste.org datacenter.

In January 2008 http://www.macaq.org/ donated hosting for the older Dells which were brought back online.

In February 2008 http://www.skyrock.com/ donated hosting and gcc13 was moved in the new datacenter.

In March 2008

The GCC Compile Farm wants to thank all the sponsor that make this project to help free software a reality.

None: CompileFarm (last edited 2008-05-09 19:59:26 by LaurentGuerby)