From: "Joseph S. Myers" <joseph@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
Mark Kettenis <mark.kettenis@xs4all.nl>,
jan.kratochvil@redhat.com, Jon.Zhou@jdsu.com,
gdb@sourceware.org, gdb-patches@sourceware.org
Subject: Re: support biarch gcore?
Date: Wed, 21 Jul 2010 22:45:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1007212244380.23882@digraph.polyomino.org.uk> (raw)
In-Reply-To: <AANLkTimQRQeRUPtRFiXuU7Z2RWfYItt07gOcZBeAYj9R@mail.gmail.com>
On Thu, 8 Jul 2010, H.J. Lu wrote:
> Very good point. There are some arch specific tests which are either
> 32bit or 64bit. Currently, we check target. It doesn't work -m32. We
> need something like
>
> /* { dg-require-effective-target lp64 } */
> /* { dg-require-effective-target ilp32 } */
I noted the issue with GDB testcases hardcoding target name tests in a
previous discussion
<http://sourceware.org/ml/gdb-patches/2010-03/msg00711.html>, and I think
adopting GCC-style effective target support would be a good solution.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2010-07-21 22:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201007062128.o66LSkNC032580@glazunov.sibelius.xs4all.nl>
2010-07-07 12:30 ` Ulrich Weigand
2010-07-08 2:35 ` Jon Zhou
2010-07-08 11:17 ` Ulrich Weigand
2010-07-08 4:47 ` H.J. Lu
2010-07-08 5:05 ` H.J. Lu
2010-07-08 11:15 ` Ulrich Weigand
2010-07-08 13:52 ` H.J. Lu
2010-07-09 15:48 ` [rfc] skip_ilp32_tests / skip_lp64_tests predicates (was: Re: support biarch gcore?) Ulrich Weigand
2010-07-09 15:56 ` H.J. Lu
2010-07-09 21:43 ` H.J. Lu
2010-07-09 22:33 ` H.J. Lu
2010-07-12 14:49 ` Ulrich Weigand
2010-07-21 22:45 ` Joseph S. Myers [this message]
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=Pine.LNX.4.64.1007212244380.23882@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Jon.Zhou@jdsu.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=uweigand@de.ibm.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).