From: Daniel Santos <daniel.santos@pobox.com>
To: Uros Bizjak <ubizjak@gmail.com>,
Mike Stump <mikestump@comcast.net>,
Iain Sandoe <iain@codesourcery.com>,
Ian Lance Taylor <ian@airs.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Subject: PING: [PATCH v2 0/2] [testsuite, libgcc] PR80759 Fix FAILs on Solaris and Darwin
Date: Mon, 17 Jul 2017 16:11:00 -0000 [thread overview]
Message-ID: <b0e442cf-e464-554d-4620-4fb2332d68b0@pobox.com> (raw)
In-Reply-To: <57df17f5-1714-a618-30a9-086c83ee7623@pobox.com>
https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00025.html
Uros,
Can you review changes for i386 please?
Mike or Iain,
Can one of you review changes for Darwin please? I'm not familiar with
the platform, although Rainer tested on Darwin for me.
Ian,
Can you review changes to libgcc please?
Thank you all!
Daniel
On 07/02/2017 12:11 AM, Daniel Santos wrote:
> This patchset addresses a number of testsuite issues for
> gcc.target/x86_64/abi/ms-sysv/ms-sysv.exp, mostly occurring on Solaris
> and Darwin. Additionally, it solves a bug in libgcc that caused link
> failures on Darwin when building with -mcall-ms2sysv-xlogues. The
> issues are detailed in the notes for each patch.
>
> I would particularly appreciate any feedback for Darwin as I am
> unfamiliar with the platform and Rainer and I have fashioned some of
> these changes by looking at other Darwin code in gcc.
>
> .../gcc.target/x86_64/abi/ms-sysv/do-test.S | 200
> ++++++++-----------
> .../gcc.target/x86_64/abi/ms-sysv/ms-sysv.c | 83 +++++++-
> .../gcc.target/x86_64/abi/ms-sysv/ms-sysv.exp | 153 +++++---------
> libgcc/config.host | 6 +-
> libgcc/config/i386/i386-asm.h | 89 +++++----
> libgcc/config/i386/resms64.S | 2 +-
> libgcc/config/i386/resms64f.S | 2 +-
> libgcc/config/i386/resms64fx.S | 2 +-
> libgcc/config/i386/resms64x.S | 2 +-
> libgcc/config/i386/savms64.S | 2 +-
> libgcc/config/i386/savms64f.S | 2 +-
> 11 files changed, 274 insertions(+), 269 deletions(-)
>
>
> Many thanks to Rainer for all of his help on this!
>
> Thanks,
> Daniel
next prev parent reply other threads:[~2017-07-17 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 6:29 [PATCH 0/2] [testsuite] PR80759 Fix test breakages on i386-pc-solaris2.* Daniel Santos
2017-05-19 6:29 ` [PATCH 1/2] [testsuite] Move non-standard parallelization support into new lib and fix flaw Daniel Santos
2017-05-19 6:50 ` [PATCH 2/2] [testsuite] PR 80759 Remove gas extensions from do-test.S, fix other problems Daniel Santos
2017-05-19 8:54 ` Rainer Orth
2017-05-20 0:38 ` Daniel Santos
2017-05-19 9:04 ` [PATCH 0/2] [testsuite] PR80759 Fix test breakages on i386-pc-solaris2.* Rainer Orth
2017-07-02 5:06 ` [PATCH v2 0/2] [testsuite, libgcc] PR80759 Fix FAILs on Solaris and Darwin Daniel Santos
2017-07-02 5:10 ` [PATCH 1/2] [testsuite] PR80759 fix tests " Daniel Santos
2017-07-02 5:10 ` [PATCH 2/2] [libgcc]: PR80759 fixes for Solaris & Darwin Daniel Santos
2017-07-17 16:11 ` Daniel Santos [this message]
2017-07-17 16:38 ` PING: [PATCH v2 0/2] [testsuite, libgcc] PR80759 Fix FAILs on Solaris and Darwin Mike Stump
2017-07-17 18:50 ` Uros Bizjak
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=b0e442cf-e464-554d-4620-4fb2332d68b0@pobox.com \
--to=daniel.santos@pobox.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@codesourcery.com \
--cc=ian@airs.com \
--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).