From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: JonY <10walls@gmail.com>
Cc: Jonathan Wakely <jwakely@redhat.com>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org,
fortran@gcc.gnu.org, Uros Bizjak <ubizjak@gmail.com>,
Mike Stump <mikestump@comcast.net>
Subject: Re: [testsuite, i386] Always check for target i?86 and x86_64
Date: Tue, 20 Jun 2017 13:35:00 -0000 [thread overview]
Message-ID: <yddy3sm3hpu.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <ba5d5df0-28d7-ba31-f433-291b862b9995@gmail.com> (JonY's message of "Tue, 20 Jun 2017 13:25:07 +0000")
JonY <10walls@gmail.com> writes:
> On 06/20/2017 01:01 PM, Rainer Orth wrote:
>> Given that there were no other comments, I've installed the patch. It
>> would still be nice if the Cygwin/MingW maintainer could comment on the
>> testcase situation for those targets.
>
> Honestly, I'm not sure how ms-bitfields work on non-Windows targets,
I just noticed that it's handled in generic code in i386.c and the
affected tests worked on the likes of Linux and Solaris ;-)
> beyond that, the patch looks like it won't change the tests that run for
> mingw/cygwin.
True: as I mentioned in the submission
https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01103.html
I didn't touch the Cygwin/MingW patches listed there except for those
where I could verify that they would/should work on any x86 target.
Maybe you can have a look a the questions raised there ("There's one
group of targets I've omitted completely"...)?
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2017-06-20 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 10:51 Rainer Orth
2017-06-15 11:31 ` Jonathan Wakely
2017-06-20 13:01 ` Rainer Orth
2017-06-20 13:25 ` JonY
2017-06-20 13:35 ` Rainer Orth [this message]
2017-06-20 14:29 ` JonY
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=yddy3sm3hpu.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=10walls@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=ubizjak@gmail.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).