Source code of CIL back-end
Hello, last week I announced that, within the R&D division of STMicroelectronics I belong to, my team decided to work about a CIL back-end for gcc (see http://gcc.gnu.org/ml/gcc/2006-06/msg00420.html). After receiving positive feedback and interest about such a back-end, I thought it's a good idea to start right now sharing the code and setting up a collaborative development environment. My preferred way to work is to open a development branch in gcc and to make it the official place for the development of the back-end. As far as I know, this can't be done until the CIL back-end is approved for a possible inclusion in gcc. In the meantime, I opened a project in a public repository; this is meant to be temporary, I will dismantle it for a gcc development branch. By the way, is there any news about the status of the CIL issue? I'm sorry to bother the list readers about this, but whom could I directly ask? Here is a link to the public project I've just mentioned: https://gna.org/projects/cil4gcc The subversion repository contains the current status of the code written by the team in STMicroelectronics. If it is useful, I can add a patch file for gcc 4.2 snapshot of 20060422 to the project files. The code is still at prototypal stage. Nevertheless, all features of ANSI C and C99 are supported. You're invited to try it; just check out the source code and launch cil32-crosstool.sh script in a newly created directory. The script configures gcc as a CIL cross-compiler and it builds it. Beware that the back-end comes with no C library (at least not yet)... you can check the assembler emitted for test C programs, but don't yet expect to compile and link programs that use it! Finally, I will attend the developers' summit next week in Ottawa. I hope it's also going to be a very good occasion to talk "live" about the back-end. Cheers, Roberto
g++ 4.1.1 Missing warning
I was surprised when this erroneous line didn't give an error:
Bifilter _bif(new Filter(),Bifilter::DELETE_ON_DESTRUCTION);
when the Bifilter constructor is defined as
class Bifilter : public Filter
{
public:
enum DestructorAction { DELETE_ON_DESTRUCTION, KEEP_ON_DESTRUCTION
};
Bifilter(
Filter* _source = 0,
Filter* _sink = 0,
DestructorAction _action = KEEP_ON_DESTRUCTION
);
...
Now obviously DELETE_ON_DESTRUCTION is zero, which is a valid pointer
assignment, so I changed its declaration to
enum DestructorAction { DELETE_ON_DESTRUCTION=1, KEEP_ON_DESTRUCTION };
but still no error.
However, this
io::Bifilter _bif(new io::Device(_s2), 1);
does give the expected error:
test.cpp:36: error: invalid conversion from 'int' to 'Filter*'
test.cpp:36: error: initializing argument 2 of 'Bifilter::Bifilter(Filter*,
Filter*,Bifilter::DestructorAction)'
Am I missing something (as usual!) or is this a bug?
Andrew Walrond
TAF tan FIFA 2006 Resimleri
Amatör film yönetmenlerimize, herzaman ilgi gösteren Türk medyasina tesekkür olarak bizde FIFA 2006 dan cektigimiz dijital resimlerimizi Türk medya mensuplariyla paylasmak istiyoruz. www.makinist.de Almanya nin baskenti Berlin de yayinladigimiz TAF (Türk Amatör Filmi) adli tv programimizi Türkiye ye tanitan medya mensuplarina tesekkür ederiz. Gelecek sezonda da Türk genc yönetmenlerimizi ve Türk Amatör Filmi ni desteklemeye devam edeceklerinden eminiz. Ayni zamanda amatör filmlerini bizlerle paylasan ve programimizda yayinlamamiza izin veren genc yönetmenlerimize de tesekkür ederiz. 2005/2006 yayin sezonunda bir cok ilke ve rekora imza atan programimiz tatile giriyor. Ekim 2006 da bir cok yenilikler programimiza devam edecegiz. SIS ve TAVLA adli kisafilmlerini ve müzik kliplerini programlarimizda yayinladigimiz ve Alman seyircisininde büyük ilgisini ceken basarili genc yönetmenimiz Biray Dalkiran in ilk sinema filmini büyük gururla sizlere duyurmak istiyoruz. ARAF 6 Ekim de sinemalarda. Genis bilgi: www.araf-film.com Herhangi bilgisayar formatinda olan, amatör filmlerinizi bekliyoruz. Yönetmenin veya oyuncularin yetenegini öne cikaran seyirciyi bilgilendiren ve ekran karsisinda eglenceli vakit gecirmesini saglayan amatör filmleri yayinlamaya devam edecegiz. Berlin Türk ve Alman seyircisinin ilgisini cekecegine inandigimiz filmlerinizi Almanca alt yazi yapip tv formatina dönüstürüp TAF adli programimizda ve internet sitemizde yayinlayacagiz. - - - - - - - - - - - - - - - - - - - - Bu mail Türkiye nin önde gelen medya mensuplarina, politikacilarina, yönetmenlerine, taninmis isimlerine, gelecek vaad eden, genc yönetmenlerimizin yurt disi basarisina duyarli olan herkese gönderilmekte. Lütfen ayda bir defa gönderdigimiz bu mailimizi spam olarak görmeyin. Genc yönetmenlerimizin yurt disindaki basarisini sizlerle paylasmak istiyoruz. Yine de listeden isminizin silinmesini istiyorsaniz lütfen bize mail gönderin ([EMAIL PROTECTED]). TAF (Türk Amatör Filmi) Genis bilgi ve FIFA 2006 Dünya Futbol Sampiyonasi Berlin resimleri: Internet: www.Makinist.de E-Mail: [EMAIL PROTECTED]
TAF tan FIFA 2006 Resimleri
Amatör film yönetmenlerimize, herzaman ilgi gösteren Türk medyasina tesekkür olarak bizde FIFA 2006 dan cektigimiz dijital resimlerimizi Türk medya mensuplariyla paylasmak istiyoruz. www.makinist.de Almanya nin baskenti Berlin de yayinladigimiz TAF (Türk Amatör Filmi) adli tv programimizi Türkiye ye tanitan medya mensuplarina tesekkür ederiz. Gelecek sezonda da Türk genc yönetmenlerimizi ve Türk Amatör Filmi ni desteklemeye devam edeceklerinden eminiz. Ayni zamanda amatör filmlerini bizlerle paylasan ve programimizda yayinlamamiza izin veren genc yönetmenlerimize de tesekkür ederiz. 2005/2006 yayin sezonunda bir cok ilke ve rekora imza atan programimiz tatile giriyor. Ekim 2006 da bir cok yenilikler programimiza devam edecegiz. SIS ve TAVLA adli kisafilmlerini ve müzik kliplerini programlarimizda yayinladigimiz ve Alman seyircisininde büyük ilgisini ceken basarili genc yönetmenimiz Biray Dalkiran in ilk sinema filmini büyük gururla sizlere duyurmak istiyoruz. ARAF 6 Ekim de sinemalarda. Genis bilgi: www.araf-film.com Herhangi bilgisayar formatinda olan, amatör filmlerinizi bekliyoruz. Yönetmenin veya oyuncularin yetenegini öne cikaran seyirciyi bilgilendiren ve ekran karsisinda eglenceli vakit gecirmesini saglayan amatör filmleri yayinlamaya devam edecegiz. Berlin Türk ve Alman seyircisinin ilgisini cekecegine inandigimiz filmlerinizi Almanca alt yazi yapip tv formatina dönüstürüp TAF adli programimizda ve internet sitemizde yayinlayacagiz. - - - - - - - - - - - - - - - - - - - - Bu mail Türkiye nin önde gelen medya mensuplarina, politikacilarina, yönetmenlerine, taninmis isimlerine, gelecek vaad eden, genc yönetmenlerimizin yurt disi basarisina duyarli olan herkese gönderilmekte. Lütfen ayda bir defa gönderdigimiz bu mailimizi spam olarak görmeyin. Genc yönetmenlerimizin yurt disindaki basarisini sizlerle paylasmak istiyoruz. Yine de listeden isminizin silinmesini istiyorsaniz lütfen bize mail gönderin ([EMAIL PROTECTED]). TAF (Türk Amatör Filmi) Genis bilgi ve FIFA 2006 Dünya Futbol Sampiyonasi Berlin resimleri: Internet: www.Makinist.de E-Mail: [EMAIL PROTECTED]
TAF tan FIFA 2006 Resimleri
Amatör film yönetmenlerimize, herzaman ilgi gösteren Türk medyasina tesekkür olarak bizde FIFA 2006 dan cektigimiz dijital resimlerimizi Türk medya mensuplariyla paylasmak istiyoruz. www.makinist.de Almanya nin baskenti Berlin de yayinladigimiz TAF (Türk Amatör Filmi) adli tv programimizi Türkiye ye tanitan medya mensuplarina tesekkür ederiz. Gelecek sezonda da Türk genc yönetmenlerimizi ve Türk Amatör Filmi ni desteklemeye devam edeceklerinden eminiz. Ayni zamanda amatör filmlerini bizlerle paylasan ve programimizda yayinlamamiza izin veren genc yönetmenlerimize de tesekkür ederiz. 2005/2006 yayin sezonunda bir cok ilke ve rekora imza atan programimiz tatile giriyor. Ekim 2006 da bir cok yenilikler programimiza devam edecegiz. SIS ve TAVLA adli kisafilmlerini ve müzik kliplerini programlarimizda yayinladigimiz ve Alman seyircisininde büyük ilgisini ceken basarili genc yönetmenimiz Biray Dalkiran in ilk sinema filmini büyük gururla sizlere duyurmak istiyoruz. ARAF 6 Ekim de sinemalarda. Genis bilgi: www.araf-film.com Herhangi bilgisayar formatinda olan, amatör filmlerinizi bekliyoruz. Yönetmenin veya oyuncularin yetenegini öne cikaran seyirciyi bilgilendiren ve ekran karsisinda eglenceli vakit gecirmesini saglayan amatör filmleri yayinlamaya devam edecegiz. Berlin Türk ve Alman seyircisinin ilgisini cekecegine inandigimiz filmlerinizi Almanca alt yazi yapip tv formatina dönüstürüp TAF adli programimizda ve internet sitemizde yayinlayacagiz. - - - - - - - - - - - - - - - - - - - - Bu mail Türkiye nin önde gelen medya mensuplarina, politikacilarina, yönetmenlerine, taninmis isimlerine, gelecek vaad eden, genc yönetmenlerimizin yurt disi basarisina duyarli olan herkese gönderilmekte. Lütfen ayda bir defa gönderdigimiz bu mailimizi spam olarak görmeyin. Genc yönetmenlerimizin yurt disindaki basarisini sizlerle paylasmak istiyoruz. Yine de listeden isminizin silinmesini istiyorsaniz lütfen bize mail gönderin ([EMAIL PROTECTED]). TAF (Türk Amatör Filmi) Genis bilgi ve FIFA 2006 Dünya Futbol Sampiyonasi Berlin resimleri: Internet: www.Makinist.de E-Mail: [EMAIL PROTECTED]
TAF tan FIFA 2006 Resimleri
Amatör film yönetmenlerimize, herzaman ilgi gösteren Türk medyasina tesekkür olarak bizde FIFA 2006 dan cektigimiz dijital resimlerimizi Türk medya mensuplariyla paylasmak istiyoruz. www.makinist.de Almanya nin baskenti Berlin de yayinladigimiz TAF (Türk Amatör Filmi) adli tv programimizi Türkiye ye tanitan medya mensuplarina tesekkür ederiz. Gelecek sezonda da Türk genc yönetmenlerimizi ve Türk Amatör Filmi ni desteklemeye devam edeceklerinden eminiz. Ayni zamanda amatör filmlerini bizlerle paylasan ve programimizda yayinlamamiza izin veren genc yönetmenlerimize de tesekkür ederiz. 2005/2006 yayin sezonunda bir cok ilke ve rekora imza atan programimiz tatile giriyor. Ekim 2006 da bir cok yenilikler programimiza devam edecegiz. SIS ve TAVLA adli kisafilmlerini ve müzik kliplerini programlarimizda yayinladigimiz ve Alman seyircisininde büyük ilgisini ceken basarili genc yönetmenimiz Biray Dalkiran in ilk sinema filmini büyük gururla sizlere duyurmak istiyoruz. ARAF 6 Ekim de sinemalarda. Genis bilgi: www.araf-film.com Herhangi bilgisayar formatinda olan, amatör filmlerinizi bekliyoruz. Yönetmenin veya oyuncularin yetenegini öne cikaran seyirciyi bilgilendiren ve ekran karsisinda eglenceli vakit gecirmesini saglayan amatör filmleri yayinlamaya devam edecegiz. Berlin Türk ve Alman seyircisinin ilgisini cekecegine inandigimiz filmlerinizi Almanca alt yazi yapip tv formatina dönüstürüp TAF adli programimizda ve internet sitemizde yayinlayacagiz. - - - - - - - - - - - - - - - - - - - - Bu mail Türkiye nin önde gelen medya mensuplarina, politikacilarina, yönetmenlerine, taninmis isimlerine, gelecek vaad eden, genc yönetmenlerimizin yurt disi basarisina duyarli olan herkese gönderilmekte. Lütfen ayda bir defa gönderdigimiz bu mailimizi spam olarak görmeyin. Genc yönetmenlerimizin yurt disindaki basarisini sizlerle paylasmak istiyoruz. Yine de listeden isminizin silinmesini istiyorsaniz lütfen bize mail gönderin ([EMAIL PROTECTED]). TAF (Türk Amatör Filmi) Genis bilgi ve FIFA 2006 Dünya Futbol Sampiyonasi Berlin resimleri: Internet: www.Makinist.de E-Mail: [EMAIL PROTECTED]
Re: !(fun) with tls
i think this is something to do with --with-sysroot. Try removing the sysroot but i am not sure well sysroot/lib should contain libc.so /lib/libc.so.6 is provided by glibc whereas /usr/lib/libc.so is provided by glibc-devel. Maybe some one experienced can help you out. On 6/22/06, NZG <[EMAIL PROTECTED]> wrote: On Thursday 22 June 2006 12:55 pm, Niklaus wrote: > sorry i didn't understand your question. I build on debian and > everything works fine for me > Please be more elaborate where it didn't > find libc.so.6. I think works, creating extra library simlinks allows the build process to see them. i.e. linking libc.so -> libc.so.6 Allows the build process to find libc. My question is, why is this necessary? libc.so.6 is already a simlink to libc-2.3.2.so Why doesn't the compiler recognize libc.so.6 as libc.so? This is the name of the simlink in the /lib directory of my target and host, and I don't see any simlinks to it. Why is this step required? Should I being doing something "cleaner" thx, NZG You have to copy the symlinks also cp -pf or do a tar > of those and then untar. Please copy cross gcc as it may help others . > On 6/22/06, NZG <[EMAIL PROTECTED]> wrote: > > Do you know why it doesn't accept libc.so.6 like standard Debian? > > Is this a patch to gcc? > > > > thx, > > NZG > > > > On Thursday 22 June 2006 11:02 am, you wrote: > > > no gcc couldn't find libc. > > > your sysroot directory doesn't have a file label libc.so* and libc.a > > > in lib or /usr/lib/ > > > > > > For the taget mips-deb-linux my directories look like this. So you > > > will have to copy them or softlink them. > > > > > > [EMAIL PROTECTED]:~/crossenv/mips-deb-linux/lib$ ls > > > ld-2.3.4.so libcrypt.so.1libnss_compat-2.3.4.so > > > libnss_nisplus.so.2 libstdc++.so.6 > > > ld.so.1 libdl-2.3.4.so libnss_compat.so.2 > > > libpcprofile.so libstdc++.so.6.0.3 > > > ldscripts libdl.so.2 libnss_dns-2.3.4.so > > > libpthread-0.10.so libsupc++.a > > > libBrokenLocale-2.3.4.so libgcc_s.so libnss_dns.so.2 > > > libpthread.so.0 libsupc++.la > > > libBrokenLocale.so.1 libgcc_s.so.1libnss_files-2.3.4.so > > > libresolv-2.3.4.so libthread_db-1.0.so > > > libSegFault.solibiberty.a libnss_files.so.2 > > > libresolv.so.2 libthread_db.so.1 > > > libanl-2.3.4.so libm-2.3.4.solibnss_hesiod-2.3.4.so > > > librt-2.3.4.so libutil-2.3.4.so > > > libanl.so.1 libm.so.6libnss_hesiod.so.2 > > > librt.so.1 libutil.so.1 > > > libc-2.3.4.so libmemusage.so libnss_nis-2.3.4.so > > > libstdc++.a libc.so.6 libnsl-2.3.4.so libnss_nis.so.2 > > > libstdc++.la libcrypt-2.3.4.so libnsl.so.1 > > > libnss_nisplus-2.3.4.so libstdc++.so > > > [EMAIL PROTECTED]:~/crossenv/mips-deb-linux/lib$ ls libc* > > > libc-2.3.4.so libc.so.6 libcrypt-2.3.4.so libcrypt.so.1 > > > [EMAIL PROTECTED]:~/crossenv/mips-deb-linux/lib$ cd .. > > > [EMAIL PROTECTED]:~/crossenv/mips-deb-linux$ ls > > > bin etc include lib sbin usr > > > [EMAIL PROTECTED]:~/crossenv/mips-deb-linux$ cd usr/lib > > > [EMAIL PROTECTED]:~/crossenv/mips-deb-linux/usr/lib$ ls > > > Mcrt1.o gcrt1.o libc.alibdl.so libnsl.a > > >libnss_nis.so libresolv.so > > > Scrt1.o libBrokenLocale.a libc.so libg.a libnsl.so > > >libnss_nisplus.so librt.a > > > crt1.o libBrokenLocale.so libc_nonshared.a libieee.a > > > libnss_compat.so libpthread.alibrt.so > > > crti.o libanl.alibcrypt.alibm.a > > > libnss_dns.so libpthread.so libthread_db.so > > > crtn.o libanl.so libcrypt.so libm.so > > > libnss_files.so libpthread_nonshared.a libutil.a > > > gconvlibbsd-compat.a libdl.a libmcheck.a > > > libnss_hesiod.so libresolv.a libutil.so > > > [EMAIL PROTECTED]:~/crossenv/mips-deb-linux/usr/lib$ > > > > > > On 6/22/06, NZG <[EMAIL PROTECTED]> wrote: > > > > On Thursday 22 June 2006 10:17 am, Niklaus wrote: > > > > > export PATH=$prefix/bin:$PATH > > > > > > > > Aha! thx, got past > > > > > > > > > make[2]: i486-linux-ar: Command not found > > > > > > > > Now I get the > > > > /home/nathan/workspace-new/SIB2.0-SDK/gcc-3.3.6-SIB//i486-linux/bin/l > > > >d: cannot find -lc > > > > > > > > error, which I'm guessing is happening because the libc it needs is > > > > not in SEARCH_DIR . > > > > > > > > My thinking was that > > > > --with-sysroot=$SYSROOT \ > > > > should add SYSROOT to binutils SEARCH_DIR, but it doesn't appear to. > > > > Is there something else I should be doing? > > > > > > > > thx, > > > > NZG > > > > > > > > > HOW I"M GOING ABOUT IT: > > > > > > > > > > #!/bin/sh > > > > > SYSROOT=$HOME/workspace-new/SIB2.0-SDK/sysroot/ > > > > > PREFIX=$HOME/workspace-new/SIB2.0-SDK/gcc-3.3.6-SIB/ > > > > > > > > > > mkdir -p binutils-
Re: !(fun) with tls
On Fri, Jun 23, 2006 at 12:30:22AM +0530, Niklaus wrote: > i think this is something to do with --with-sysroot. > Try removing the sysroot but i am not sure well sysroot/lib should > contain libc.so > > /lib/libc.so.6 is provided by glibc whereas /usr/lib/libc.so is > provided by glibc-devel. > > Maybe some one experienced can help you out. Don't crosspost to gcc and gcc-help, please. This is not a question about GCC development. -- Daniel Jacobowitz CodeSourcery
Re: !(fun) with tls
> /lib/libc.so.6 is provided by glibc whereas /usr/lib/libc.so is > provided by glibc-devel. Ah, if this is true then I probably need to be building against a sysroot containing glibc-devel. I'll try that, thx. NZG
What is baseline for the testsuite?
Hi, After following the mailing list for a while I got impression that it is not trivial to interpret "make -k check" results, i.e. if you get FAILs while testing your changes, that does not necessarily mean that your code actually broke something, as FAILs are rather common. So I guess that there is no baseline as such, and the only meaningful way to use the results is to compare testsuite outputs with and without your changes? -- Laurynas
Re: What is baseline for the testsuite?
On Jun 22, 2006, at 12:25 PM, Laurynas Biveinis wrote: So I guess that there is no baseline as such, and the only meaningful way to use the results is to compare testsuite outputs with and without your changes? Depends upon what you're doing... For the normal regression test while developing work for gcc, it is customary to have 2 runs and compare them. If you're doing up a new port, and want it to work well, then the absolute, there should be no unexpected failures is a good place to aim for. You can consider each email of results to the gcc tests results list to be a baseline, in that case, we have oodles of baselines.
Re: What is baseline for the testsuite?
> So I guess that there is no baseline as such, and the only > meaningful way to use the results is to compare testsuite outputs > with and without your changes? That's what I always do. Hence the "no regressions" we report; they're before/after regressions. Very important to diff the two source trees to make sure you don't have unrelated differences that might corrupt your regression analysis, too.
Re: What is baseline for the testsuite?
> If you're doing up a new port, and want it to work well, then the > absolute, there should be no unexpected failures is a good place to > aim for. It's a wonderful absolute, but not always practical. I keep a history of test results for my ports, with a goal of "no regressions" relative to those. It still leaves the "where do you start" question unanswered. I try to balance "needs to work" with "sometime this century" ;-)
Re: What is baseline for the testsuite?
Laurynas Biveinis wrote: > Hi, > > After following the mailing list for a while I got impression that it > is not trivial to interpret "make -k check" results, i.e. if you get > FAILs while testing your changes, that does not necessarily mean that > your code actually broke something, as FAILs are rather common. Well, not common. I think on i686, there are a couple fails that are known (4 or 5) out of thousands of testcases. > > So I guess that there is no baseline as such, and the only meaningful > way to use the results is to compare testsuite outputs with and > without your changes? > More or less. You can look at the gcc-testresults archives, and your baseline should match up pretty closely with one of hte ones there.
HP/UX maintainers
It is my pleasure to announce that the steering committee has appointed Steve Ellcey and John David Anglin maintainers of our HP/UX ports, which the two of them have been caring and feeding for some time now. Please adjust your entries in our MAINTAINERS file, Dave and Steve! Congratulations, and Happy Hacking! Gerald
Re: Wrong link?
On Wed, 24 May 2006, Bill Gatliff wrote: > Indeed, "bitrotted" is in fact a better description of what is happening. I have tweaked the ChangeLog entry to say "gone", which is even more neutral, and will do the same on the 4.1 branch shortly. Gerald
Re: Wrong link?
Gerald: Gerald Pfeifer wrote: On Wed, 24 May 2006, Bill Gatliff wrote: Indeed, "bitrotted" is in fact a better description of what is happening. I have tweaked the ChangeLog entry to say "gone", which is even more neutral, and will do the same on the 4.1 branch shortly. Gerald Thanks! b.g. -- Bill Gatliff [EMAIL PROTECTED]
Re: Usage of -ftrapv
On 19/06/06, Eric Botcazou <[EMAIL PROTECTED]> wrote: > By the way, -ftrapv only works on integral types. When it works. Last time I took a look, it was easily wiped out by optimization. So, it is of no use then... :-( -- Eric Botcazou -- Paulo Jorge Matos - pocm at sat inesc-id pt Web: http://sat.inesc-id.pt/~pocm Computer and Software Engineering INESC-ID - SAT Group
gcc-4.0-20060622 is now available
Snapshot gcc-4.0-20060622 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.0-20060622/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.0 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_0-branch revision 114912 You'll find: gcc-4.0-20060622.tar.bz2 Complete GCC (includes all of below) gcc-core-4.0-20060622.tar.bz2 C front end and core compiler gcc-ada-4.0-20060622.tar.bz2 Ada front end and runtime gcc-fortran-4.0-20060622.tar.bz2 Fortran front end and runtime gcc-g++-4.0-20060622.tar.bz2 C++ front end and runtime gcc-java-4.0-20060622.tar.bz2 Java front end and runtime gcc-objc-4.0-20060622.tar.bz2 Objective-C front end and runtime gcc-testsuite-4.0-20060622.tar.bz2The GCC testsuite Diffs from 4.0-20060615 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.0 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
Re: Source code of CIL back-end
Roberto COSTA wrote: > Hello, > last week I announced that, within the R&D division of > STMicroelectronics I belong to, my team decided to work about a CIL > back-end for gcc (see http://gcc.gnu.org/ml/gcc/2006-06/msg00420.html). > After receiving positive feedback and interest about such a back-end, I > thought it's a good idea to start right now sharing the code and setting > up a collaborative development environment. > My preferred way to work is to open a development branch in gcc and to > make it the official place for the development of the back-end. > As far as I know, this can't be done until the CIL back-end is approved > for a possible inclusion in gcc. In the meantime, I opened a project in > a public repository; this is meant to be temporary, I will dismantle it > for a gcc development branch. > By the way, is there any news about the status of the CIL issue? > I'm sorry to bother the list readers about this, but whom could I > directly ask? As Joe Buck, a Steering Committee member said, you need to talk to RMS directly and get him to accept the idea, before we can do anything about it.
