From: Alan Modra <amodra@gmail.com>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: Tamar Christina <Tamar.Christina@arm.com>,
binutils <binutils@sourceware.org>, nd <nd@arm.com>
Subject: Re: [PATCH] Add support for non-contiguous memory regions
Date: Thu, 20 Feb 2020 08:15:00 -0000 [thread overview]
Message-ID: <20200220081517.GX5570@bubble.grove.modra.org> (raw)
In-Reply-To: <CAKdteObVAUJd-z4U1U3DDP-H-CWSD+Z=YiDKLXj8RasVGEr4tg@mail.gmail.com>
On Thu, Feb 20, 2020 at 05:37:03AM +0100, Christophe Lyon wrote:
> Or should I just copy & paste that list from your email and
> for i in <that-list>
> do
> configure --target=$i
> make all check
> done
Yes, more or less. No need to build gdb though for binutils changes,
unless you're messing with libbfd or libopcodes API. I build with
--disable-nls --enable-plugins \
--disable-gdb --disable-gdbserver --disable-sim --disable-readline \
--disable-libdecnumber --enable-obsolete --target=$i
Parallel builds work too, except for m68hc11 and m68hc12 which write
to source directories.
I also build --enable-targets=all --enable-nls with a recent 64-bit
gcc, an older gcc, and with gcc -m32 to pick up any 32 bit problems.
My current target list is:
aarch64-elf
aarch64-linux
aarch64_be-linux-gnu_ilp32
alpha-dec-vms
alpha-linux
alpha-linuxecoff
alpha-netbsd
alpha-unknown-freebsd4.7
am33_2.0-linux
arc-elf
arc-linux-uclibc
arm-elf
arm-linuxeabi
arm-nacl
arm-netbsdelf
arm-nto
arm-pe
arm-symbianelf
arm-vxworks
arm-wince-pe
armeb-linuxeabi
avr-elf
bfin-elf
bfin-linux-uclibc
bpf-none
cr16-elf
cris-elf
cris-linux
crisv32-linux
crx-elf
csky-elf
csky-linux
d10v-elf
d30v-elf
dlx-elf
epiphany-elf
fr30-elf
frv-elf
frv-linux
ft32-elf
h8300-elf
h8300-linux
hppa-hp-hpux10
hppa-linux
hppa64-hp-hpux11.23
hppa64-linux
i386-bsd
i386-darwin
i386-lynxos
i586-linux
i686-nacl
i686-nto
i686-pc-beos
i686-pc-elf
i686-pe
i686-vxworks
ia64-elf
ia64-freebsd5
ia64-hpux
ia64-linux
ia64-netbsd
ia64-vms
ip2k-elf
iq2000-elf
lm32-elf
lm32-linux
m32c-elf
m32r-elf
m32r-linux
m68hc11-elf
m68hc12-elf
m68k-elf
m68k-linux
mcore-elf
mcore-pe
mep-elf
metag-linux
microblaze-elf
microblaze-linux
mips-linux
mips-sgi-irix6
mips-vxworks
mips64-linux
mips64-openbsd
mips64el-openbsd
mipsel-linux-gnu
mipsisa32el-linux
mipstx39-elf
mmix
mn10200-elf
mn10300-elf
moxie-elf
msp430-elf
mt-elf
nds32be-elf
nds32le-linux
nios2-linux
ns32k-netbsd
ns32k-pc532-mach
or1k-elf
or1k-linux
pdp11-dec-aout
pj-elf
powerpc-aix5.1
powerpc-aix5.2
powerpc-eabisim
powerpc-eabivle
powerpc-freebsd
powerpc-linux
powerpc-nto
powerpc-wrs-vxworks
powerpc64-freebsd
powerpc64-linux
powerpc64le-linux
powerpcle-cygwin
powerpcle-elf
pru-elf
riscv32-elf
riscv64-linux
rl78-elf
rs6000-aix4.3.3
rs6000-aix5.1
rs6000-aix5.2
rx-elf
s12z-elf
s390-linux
s390x-linux
score-elf
sh-linux
sh-nto
sh-pe
sh-rtems
sh-vxworks
shle-unknown-netbsdelf
sparc-elf
sparc-linux
sparc-sun-solaris2
sparc-vxworks
sparc64-linux
spu-elf
tic30-unknown-coff
tic4x-coff
tic54x-coff
tic6x-elf
tilegx-linux
tilepro-linux
v850-elf
vax-netbsdelf
visium-elf
wasm32
x86_64-cloudabi
x86_64-linux
x86_64-nacl
x86_64-pc-linux-gnux32
x86_64-rdos
x86_64-w64-mingw32
xc16x-elf
xgate-elf
xstormy16-elf
xtensa-elf
z80-coff
z80-elf
z8k-coff
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2020-02-20 8:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 12:34 Christophe Lyon
2020-02-14 13:02 ` Tamar Christina
2020-02-14 13:54 ` Christophe Lyon
2020-02-19 7:19 ` Alan Modra
2020-02-19 12:28 ` Christophe Lyon
2020-02-19 22:23 ` Alan Modra
2020-02-20 4:37 ` Christophe Lyon
2020-02-20 8:15 ` Alan Modra [this message]
2020-02-20 9:00 ` Christophe Lyon
2020-02-28 17:31 ` Christophe Lyon
2020-03-09 13:10 ` Christophe Lyon
2020-03-13 14:21 ` Nick Clifton
2020-03-13 14:46 ` Christophe Lyon
2020-06-02 12:49 ` Alexander Fedotov
2020-06-03 12:48 ` Christophe Lyon
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=20200220081517.GX5570@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=Tamar.Christina@arm.com \
--cc=binutils@sourceware.org \
--cc=christophe.lyon@linaro.org \
--cc=nd@arm.com \
/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).