This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug d/87824] x86_64-linux multilib issues
- From: "rguenther at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 12 Nov 2018 08:13:58 +0000
- Subject: [Bug d/87824] x86_64-linux multilib issues
- Auto-submitted: auto-generated
- References: <bug-87824-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87824
--- Comment #7 from rguenther at suse dot de <rguenther at suse dot de> ---
On Sun, 11 Nov 2018, johannespfau at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87824
>
> Johannes Pfau <johannespfau at gmail dot com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |johannespfau at gmail dot com
>
> --- Comment #5 from Johannes Pfau <johannespfau at gmail dot com> ---
> Iain, is there a specific reason why we don't have i686 on the GDC/buildkite
> CI? We could simply run a QEMU/KVM VM on a x86_64 host for this.
>
> And when running the testsuite on multilib, is it now running all tests (test
> suite and druntime, phobos) for all multilib variants? I think last time I
> checked, multilib testing tested only the main variant for some reason.
To check other variants you have to do sth like
make -jN -k check RUNTESTFLAGS="--target_board=unix/\{,-m32\}"
if you have a x32 runtime you can add ,-mx32 as well.