From mint-bounce@lists.fishpool.fi Mon Apr 27 15:35:59 2009 Date: Mon, 27 Apr 2009 22:06:02 +0300 From: "ggn (HOL)" X-Priority: 3 (Normal) Message-ID: <1751625062.20090427220602@hol.gr> To: mint@fishpool.com Subject: [MiNT] Re[2]: GCC 4.4.0 cross-compiler available In-Reply-To: <49F5F660.2020904@freesbee.fr> References: <49F5E4F5.2060309@freesbee.fr> <1240855601.9798.28.camel@localhost> <49F5F660.2020904@freesbee.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Virus-Scanned: ClamAV 0.94.2/9295/Mon Apr 27 15:28:31 2009 on takeit01.mail.dc.hol.net X-Virus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: ggn@hol.gr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id n3RJZvu4032071 Hello Vincent, Monday, April 27, 2009, 9:16:00 PM, you wrote: > Alan Hourihane wrote: >> I'm wondering if we should start sending the patches upstream so we can >> keep the patchset smaller for future releases ?? > Sure ! It would be the best. > However, I think there is one problem for that (but no definite proof). > The GCC team tries to get rid of the a.out object file format, and we still > use it. So I don't think the GCC team will accept our patches, even if we > work hard to keep them up to date. > The good news is that the MiNT patch for GCC is absolutely not complicated > (in opposition of the binutils one), it is mainly one clean configuration > file plus minor insertions. Everything is clean, done in the normal GCC way. > So that is another good reason to switch to the ELF object file format ! Guys, I just read this from http://gcc.gnu.org/gcc-4.4/changes.html: Support for a number of older systems and recently unmaintained or untested target ports of GCC has been declared obsolete in GCC 4.4. Unless there is activity to revive them, the next release of GCC will have their sources permanently *removed*. The following ports for individual systems on particular architectures have been obsoleted: -Generic a.out on IA32 and m68k (i[34567]86-*-aout*, m68k-*-aout*) -Generic COFF on ARM, H8300, IA32, m68k and SH (arm-*-coff*, armel-*-coff*, h8300-*-*, i[34567]86-*-coff*, m68k-*-coff*, sh-*-*). This does not affect other more specific targets using the COFF object format on those architectures, or the more specific H8300 and SH targets (h8300-*-rtems*, h8300-*-elf*, sh-*-elf*, sh-*-symbianelf*, sh-*-linux*, sh-*-netbsdelf*, sh-*-rtems*, sh-wrs-vxworks). -2BSD on PDP-11 (pdp11-*-bsd) -AIX 4.1 and 4.2 on PowerPC (rs6000-ibm-aix4.[12]*, powerpc-ibm-aix4.[12]*) -Tuning support for Itanium1 (Merced) variants. Note that code tuned for Itanium2 should also run correctly on Itanium1. I think it would be best to act fast on this... -- Best regards, ggn mailto:ggn@hol.gr