sites

public wiki contents of suckless.org
git clone git://git.suckless.org/sites
Log | Files | Refs

commit 6a02677ebc000c07fdceb94beccfabdfaacb7637
parent d3e616dd0985bc54c2e8154cdb34b3ded8926967
Author: arg@www.suckless.org <unknown>
Date:   Mon,  9 Mar 2009 14:03:24 +0000

update, added gottox to the list of mentors
Diffstat:
Mwww.suckless.org/GSoC2009.md | 19++++++++++---------
1 file changed, 10 insertions(+), 9 deletions(-)

diff --git a/www.suckless.org/GSoC2009.md b/www.suckless.org/GSoC2009.md @@ -50,6 +50,7 @@ Summer of Code 2009: * Uriel <<uriel99@gmail.com>> * Kai Hendry <<kai.hendry@gmail.com>> * pancake <<pancake@gmail.com>> +* Enno 'Gottox' Boland <<gottox@gmail.com>> * ...more to be announced... If you want to act as a mentor as well, please contact Anselm before you @@ -141,20 +142,20 @@ and similiar programs. We'd like to see a modern C99 compiler which performs reasonable well and only supports C, not C++. gcc is too slow and too focused on language-agnostics and particularly focused on its C++ support. We got the impression that most open -source software is written in C and makes no use of C++, so that it would be -desirable to have a modern C99 compiler for the x86 and arm architecture. +source software is written in C and makes no use of C++, so that it's +desirable to have a modern C99 compiler for the x86 and arm architectures. -We are also concerned about recent attempts by certain parties to implement the -C frontend for gcc in C++. We believe that is a bad decision in general (due to -demanding C++ as bootstrapping environment) and would like to get rid from the -gcc dependency for these reasons. +We are also concerned about recent attempts to implement the C front-end of gcc +in C++. We believe that is a bad decision in general (due to demanding C++ as +bootstrapping environment) and would like to get rid from the gcc dependency +for these reasons. We'd like to see that the C99 compiler is able to build recent linux kernels as a test bed. Due to the high difficulty we believe that this project might consist of up to -3 students concentrating on different parts (parsing/lexing/front-end/syntax -tree being 1 student, AST optimization/reverse engineering being another -student and code generator being a third student). +3 students concentrating on different parts (1 student for the front-end, 1 +student for the AST optimization/normalization, 1 or 2 students for the x86 and +arm backends). [FAQ]: http://code.google.com/opensource/gsoc/2009/faqs.html#0_1_ideas_5167658354380897_772