Borut's TODO list - roybaer/sdcc-wiki GitHub Wiki

Table of Contents SF project maintenance: SDCPP: SDCC front end: Targets: Regression tests: Build process: Packaging: Utilities: Documentation: SDCC Release Wiki: SDCC web page:

• Migrate SDCC from CVS to Subversion (See CVS To Subversion Migration Plan). (DONE)
• Use VPATH functionality for sdcc snapshot builds:
  • Sdcc sources are checked out to the shared directory, which is seen from all platforms. This is done on shell.cf.sourceforge.net machine which has a relatively new version of the svn client: 1.2.1. All other machines create local build directories. (DONE)
  • Still missing some locking mechanism

• synchronize with latest version GNU libcpp (DONE 2007-06-01 - synchronized with GCC 4.2.0)
  • See the SDCPP history
• integrate sdcpp into sdcc by using GNU libcpp
• enable use of precompiled headers
• get rid of diagnistic.[ch], pretty-print.[ch], c-pretty-print.[ch], ... used just for error, warning, ... message formatting (DONE)

• (2007-05-20) implement http://sourceforge.net/tracker/index.php?func=detail&aid=1204438&group_id=599&atid=350599 (DONE 2009-07-15 by Frieder Ferlemann)
• (2007-05-20) implement compilation of more than one source file. The following warning is displayed if more of one c source file is specified on command line:

 "warning 120: cannot compile more than one source file. file 'x.c' ignored" <br>
 probably the GCC front end can be reused

• use memory buffers instead of temporary files (DONE)

• PIC, PIC16:
  • separate device file instead device.c (DONE by Raphael Neider)
• move target specific options from src/SDCCmain.c to src/<target></target>/main.c (DONE 2007-06-18)

• The rule for function names is '&lt;sup&gt;test\w+\(\w+\)' (from support/regression/generate-cases.py), which is not enough flexible by my opinion. Better option would be '&lt;/sup&gt;\W*test\w*\W*\(\W*void\W*\)', which allows spaces around the function definition and a void parameter list, optionally surrounded by spaces. (DONE 2007-06-07)
• Run Windows regression test on a Linux machine via Wine (DONE 2010-11-05)
• Run 64bit Windows regression test on a Linux machine via 64bit Wine (DONE 2011-09-01)

• Integrate building of SDCC documentation into the standard snapshot build procedure (DONE)
• Mac OSX and solaris builds (DONE)
• IBM openpower-linux snapshot builds (DONE)
• Update NSIS (DONE 2007-05-05 - updated to v2.27)
• Update LyX (DONE - 1.4.4 on Erik's cf-x86 machine)
• Update GCC cross compiler (DONE 2007-06-01 - updated to 4.2.0)
• Use VPATH in makefiles (DONE by Bernhard Held)
• pic and pic16 regression tests using gpsim simulator (DONE - pic16 regression tests are executed on Erik's cf-x86 machine) (2007-03-20 pic16 regression test removed from the snapshot build, requested by Frieder, Raphael and Maarten)
  • current pic16 regression test results can be found at http://sdcc.sourceforge.net/regression_test_results/amd64-unknown-linux2.3
• (2007-03-24) Build unified binaries on MacOS X (see: http://developer.apple.com/technotes/tn2005/tn2137.html, http://developer.apple.com/documentation/MacOSX/Conceptual/universal_binary/index.html, http://developer.apple.com/documentation/Porting/Conceptual/PortingUnix/PortingUnix.pdf) (DONE 2007-07-28)
• (2007-03-24) Implement "Distributed Compile Farm": (DONE 2007-03-28)
  • several DCF build machines sending builds to
  • DCF mediator sending builds to
  • DCF WEB repository - in out case SF WEB
• (2007-03-28) Implement "Distributed Compile Farm" in perl as a daemon (see: http://www.perlmonks.org/?node_id=478839)
• Windows 64bit cross-compiled build using mingw_w64 toolchain (DONE 2011-08-31)

• Win32 setup: include library sources (DONE)
• Win64 setup (NSIS): detection if installing on 64bit Windows (2011-09-01 DONE)
  • 64bit binaries should be installed to "Program Files" instead if "Program Files (x86)" (2011-09-01 DONE)

• use ar format libraries, see http://www.iecc.com/linker/ (DONE 2009-01-08)
• sdcdb: native mingw32 compilation (Current status: partially done, not tested) (DONE)
• ucsim: native mingw32 compilation - serial module has to be rewritten (DONE)
• asm: true -o support (to be verified, related to http://sourceforge.net/tracker/index.php?func=detail&aid=1065028&group_id=599&atid=350599)
• generate ar format libraries and include them in the packages (DONE 2009-01-19)

• review all SDCC documents:
  • sdcc development documentation moved from doc to sdcc wiki (DONE 2011-08-03)

• Find a place where to put SDCC Release Wiki (see https://sourceforge.net/docs/E07/, "Group Directories are Read-Only") WikkiTikkiTavi (DONE)
• Send sdcc-devel mailing list a notification on SDCC Realease Wiki update (DROPPED - it seems that sendig e-mail from php on sdcc web server doesn't work)
• Move the wiki to the SF officially supported wiki when available and rename it to "SDCC Development Wiki" or just "SDCC Wiki" (DONE 2007-06-12)

• add regression test results to the SDCC web page (DONE)
• automatic update from sdcc-web as a part of snapshot build (DONE)
• wiki pages never expire (set $ExpireLen = 0 in tavi/tavi_sdcc/lib/defaults.php) (DONE 2007-03-10)
• integrate SDCC snapshots builds with SourceForge FRS (DONE 2010-08-29)
• Store regression test restlts in the database: (DONE 2011-05-22)
  1. complete table download in CSV format (DONE 2011-05-22)
     1. download the full database in compressed format (probably bzip2)
  2. table download in CSV format, depending on criteria (platform, target, build_number, date, regtest_name) (DONE 2011-05-29)
  3. displaying regtest results, depending on criteria (platform, target, build_number, date, regtest_name) (DONE 2011-05-29)
  4. displaying differences between two regression test results (build_number, date), depending on criteria (platform, target, regtest_name) (DONE 2011-06-08)
     1. colorize the columns from different builds / ports / targets
     2. colorize the rows where results are different
     3. on rows where results are different: colorize the cells with max and min values