From: Richard Earnshaw <rearnsha@arm.com>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: Release 2.21 - rough schedule
Date: Mon, 20 Sep 2010 15:48:00 -0000 [thread overview]
Message-ID: <1284997687.13878.32.camel@e102346-lin.cambridge.arm.com> (raw)
In-Reply-To: <20100918025913.GG16874@bubble.grove.modra.org>
On Sat, 2010-09-18 at 12:29 +0930, Alan Modra wrote:
> These are the testsuite results I currently see on x86-linux building
> the targets I regularly test:
> alpha-dec-vms alpha-linux alpha-linuxecoff alpha-netbsd alpha-unknown-freebsd4.7 arc-elf arm-aout arm-coff arm-epoc-pe arm-linux arm-netbsdelf arm-none-eabi arm-nto arm-pe arm-symbianelf arm-vxworks arm-wince-pe avr-elf bfin-elf cr16-elf cris-elf crisv32-linux crx-elf d10v-elf d30v-elf dlx-elf fr30-elf frv-elf frv-linux h8300-elf h8300-rtems hppa-linux hppa-hp-hpux10 hppa64-hp-hpux11.11 hppa64-hp-hpux11.23 hppa64-linux i370-linux i386-lynxos i386-netware i386-linuxaout i586-aout i586-coff i586-linux i686-pc-beos i686-pc-elf i686-pe i860-stardent-elf i960-elf ia64-elf ia64-freebsd5 ia64-hpux ia64-linux ia64-netbsd ia64-vms ip2k-elf iq2000-elf lm32-elf m32c-elf m32r-elf m68hc11-elf m68hc12-elf m68k-elf m68k-linux m68k-netbsd m68k-rtems m68k-uclinux mcore-elf mcore-pe mep-elf microblaze-elf mips-ecoff mips-linux mips64-linux mipsel-linux-gnu mipsisa32el-linux mmix mn10200-elf mn10300-elf moxie-elf ms1-elf msp430-elf ns32k-netbsd or32-elf pdp11-dec-aout pj-elf powerpc-eabisim powerpc-linux powerpc-nto powerpc-wrs-vxworks powerpc64-linux ppc-lynxos rs6000-aix4.3.3 rs6000-aix5.1 rx-elf s390-linux s390x-linux sh-linux sh-nto sh-pe sh-rtems sh64-elf shl-unknown-netbsdelf sparc-aout sparc-coff sparc-linux sparc64-linux spu-elf tic30-unknown-aout tic30-unknown-coff tic4x-coff tic54x-coff tic6x-elf tx39-elf v850-elf vax-netbsdelf x86_64-linux x86_64-mingw32 xscale-coff xscale-elf xstormy16-elf xtensa-elf z8k-coff
>
So arm-linux isn't very interesting these days, and nor is arm-aout
(which I'm surprised we still claim to support at all). But
arm-linux-gnueabi is very important (as its a primary GCC target).
R.
next prev parent reply other threads:[~2010-09-20 15:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 14:09 Tristan Gingold
2010-09-07 16:38 ` Doug Kwan (關振德)
2010-09-18 2:59 ` Alan Modra
2010-09-20 15:48 ` Richard Earnshaw [this message]
2010-09-21 0:32 ` Alan Modra
2010-09-22 15:22 ` Tejas Belagod
2010-09-22 19:31 ` Richard Sandiford
2010-09-22 22:58 ` Maciej W. Rozycki
2010-09-23 7:17 ` Tristan Gingold
2010-09-23 12:19 ` Maciej W. Rozycki
2010-09-18 7:31 ` Matt Rice
2010-09-21 9:24 ` Mike Frysinger
2010-09-21 9:26 ` Tristan Gingold
2010-09-21 9:28 ` Kai Tietz
2010-09-21 9:31 ` Tristan Gingold
2010-09-21 9:44 ` Kai Tietz
2010-09-23 5:11 ` Dave Korn
2010-09-23 7:33 ` Tristan Gingold
2010-10-21 12:33 ` Release 2.21 - schedule Tristan Gingold
2010-11-03 14:12 ` Release 2.21 - branch on Friday ? Tristan Gingold
2010-11-04 2:40 ` Dave Korn
2010-11-04 8:11 ` Tristan Gingold
2010-11-05 9:24 ` Branch 2.21 created Tristan Gingold
2010-12-08 19:38 ` Andreas Schwab
2010-12-08 23:44 ` Alan Modra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1284997687.13878.32.camel@e102346-lin.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).