From: Doug Evans <dje@google.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] kfail longjmp.exp tests due to bug 9270
Date: Fri, 19 Mar 2010 03:29:00 -0000 [thread overview]
Message-ID: <e394668d1003182029k73e47694vbeb6b7bfb295ec8c@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1003190055000.23618@digraph.polyomino.org.uk>
On Thu, Mar 18, 2010 at 5:58 PM, Joseph S. Myers
<joseph@codesourcery.com> wrote:
> On Thu, 18 Mar 2010, Doug Evans wrote:
>
>> +setup_kfail "gdb/9270" "x86_64-*-linux*"
>
> What will happen for i686-*-linux* --enable-64-bit-bfd (running tests with
> -m64)? What about x86_64 running tests with -m32? Both i?86-* and
> x86_64-* can cover both 32-bit and 64-bit configurations.
>
> What you want is (IA32 or x86_64 GNU/Linux) and (64-bit multilib), I
> think. In GCC such tests would use the lp64 effective-target, but I don't
> know what the GDB equivalent is.
I run 64x32 tests regularly here.
The way I do it is to hack site.exp to set host_triplet, etc. to i686-linux.
Done this way, nothing further is needed, in so far as handling
{32,64}-cross-{64,x32}.
[I'm leaving as a separate discussion whether we need to xfail these
for i686-linux too. It passes here, but I gather it fails with more
recent glibc's]
next prev parent reply other threads:[~2010-03-19 3:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 22:16 Doug Evans
2010-03-18 22:33 ` Mark Kettenis
2010-03-18 23:42 ` Doug Evans
2010-03-18 23:41 ` Doug Evans
2010-03-19 0:58 ` Joseph S. Myers
2010-03-19 3:29 ` Doug Evans [this message]
2010-03-19 1:50 ` Tom Tromey
2010-03-19 2:19 ` Joseph S. Myers
2010-03-19 1:46 ` Daniel Jacobowitz
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=e394668d1003182029k73e47694vbeb6b7bfb295ec8c@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.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