public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: JonY <10walls@gmail.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
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 14:29:00 -0000	[thread overview]
Message-ID: <5fe951cb-010d-dc73-d393-3d7d7f977efc@gmail.com> (raw)
In-Reply-To: <yddy3sm3hpu.fsf@CeBiTec.Uni-Bielefeld.DE>


[-- Attachment #1.1: Type: text/plain, Size: 2146 bytes --]

On 06/20/2017 01:35 PM, Rainer Orth wrote:
> 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 ;-)

gcc/testsuite/gcc.dg/array-quals-1.c		asm bits probably won't work due to object format difference
gcc/testsuite/gcc.dg/lto/20091013-1_1.c		I'm not familiar with LTO enough to comment on it
gcc/testsuite/gcc.dg/lto/20091013-1_2.c		dto.
gcc/testsuite/gcc.dg/pr32370.c			This probably should be safe to enable for all.
gcc/testsuite/gcc.dg/pr50251.c			dto.
gcc/testsuite/gcc.dg/tls/thr-cse-1.c		I think this should stay as is.
gcc/testsuite/gcc.dg/weak/weak-15.c		ELF weak symbols don't really work on Windows PE format and are known to be broken
gcc/testsuite/gcc.dg/weak/weak-16.c		dto.
gcc/testsuite/gcc.dg/weak/weak-2.c		dto.
gcc/testsuite/gcc.dg/weak/weak-3.c		dto.
gcc/testsuite/gcc.dg/weak/weak-4.c		dto.
gcc/testsuite/gcc.dg/weak/weak-5.c		dto.
libffi/testsuite/libffi.call/cls_longdouble_va.c iirc libffi hasn't been ported for 64bit Windows



gcc/testsuite/g++.dg/abi/bitfield3.C		Should remain 32bit specific
gcc/testsuite/g++.dg/ext/dllexport3.C		Should be x86_64-*-cygwin too
gcc/testsuite/g++.dg/ext/selectany1.C		dto. 
gcc/testsuite/g++.dg/ext/selectany2.C		dto. 
gcc/testsuite/g++.old-deja/g++.ext/attrib5.C	Probably broken due to the underscore prefix in asm names for 32bit mingw/cygwin
gcc/testsuite/gcc.dg/dll-3.c			Should be x86_64-*-cygwin too
gcc/testsuite/gcc.dg/dll-4.c			dto.
gcc/testsuite/gcc.dg/dll-5.c			dto.
gcc/testsuite/gcc.dg/dll-8.c			dto.
gcc/testsuite/gcc.dg/tree-ssa/loop-1.c		dto.
gcc/testsuite/gcc.target/i386/fastcall-1.c	Keep as is, x86 specific test case.

I can't comment on the ARM mingw* port, I have no experience with it.




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

      reply	other threads:[~2017-06-20 14:29 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
2017-06-20 14:29         ` JonY [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=5fe951cb-010d-dc73-d393-3d7d7f977efc@gmail.com \
    --to=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=ro@CeBiTec.Uni-Bielefeld.DE \
    --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).