From: Uros Bizjak <ubizjak@gmail.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, crazylht@gmail.com
Subject: Re: [PATCH] testsuite, X86, Darwin: Fix bf16 ABI tests for Mach-O/macOS ABI.
Date: Mon, 5 Dec 2022 11:37:41 +0100 [thread overview]
Message-ID: <CAFULd4Y_O0v5zx=2jytyw5EuMWArF=tAgfH0qCXs6WK4dzkQzQ@mail.gmail.com> (raw)
In-Reply-To: <47BE3C16-6C72-4F13-94D7-9754BD3DEE77@sandoe.co.uk>
On Sun, Dec 4, 2022 at 9:30 PM Iain Sandoe <iain@sandoe.co.uk> wrote:
>
>
>
> > On 4 Dec 2022, at 20:20, Uros Bizjak via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
> >
> > On Sun, Dec 4, 2022 at 12:51 PM Iain Sandoe <iains.gcc@gmail.com> wrote:
> >>
> >> This is almost a completely Darwin-local patch, but there is one (repeated)
> >> place where a general change is needed - which is in making xmm_regs and
> >> x87_regs extern in the three copies of args.h (this is consistent with the
> >> other saved vars). These fails represent most of the current testsuite noise
> >> on x86 Darwin.
> >>
> >> tested on x86-64 Darwin and Linux.
> >>
> >> OK for master?
> >> Iain
> >>
> >> -- >8 --
> >>
> >> These tests have failed since introduction since they assume that the
> >> assembler output is ELF and that the ABI targeted supports the addressing.
> >>
> >> For Darwin, Mach-O and ABI we need to make several changes:
> >> 1. Use the __USER_LABEL__PREFIX__
> >> 2. Remove the use of ELF-specific constructs (.size, .type etc.)
> >> 3. We cannot make direct access to common variables in the ABI, so that we
> >> must move these to BSS.
> >>
> >> Since that set is quite significant, I elected to make a separate source
> >> section for Darwin. This is introduced by #elif defined(__APPLE__) because
> >> __MACH__ is also used by HURD.
> >>
> >> There are potentially other X86 targets (e.g. XCOFF) that could have yet
> >> more changes, so I added a catchall section that #errors if the object format
> >> is neither ELF or Mach-O.
> >>
> >> Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
> >>
> >> gcc/testsuite/ChangeLog:
> >>
> >> * gcc.target/x86_64/abi/bf16/args.h:
> >> * gcc.target/x86_64/abi/bf16/asm-support.S:
> >> * gcc.target/x86_64/abi/bf16/m256bf16/args.h:
> >> * gcc.target/x86_64/abi/bf16/m256bf16/asm-support.S:
> >> * gcc.target/x86_64/abi/bf16/m512bf16/args.h:
> >> * gcc.target/x86_64/abi/bf16/m512bf16/asm-support.S:
> >
> > Missing descriptions in ChangeLog entry.
>
> oops, here:
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/x86_64/abi/bf16/args.h: Make xmm_regs, x87_regs extern.
> * gcc.target/x86_64/abi/bf16/m256bf16/args.h: Likewise.
> * gcc.target/x86_64/abi/bf16/m512bf16/args.h: Likewise.
> * gcc.target/x86_64/abi/bf16/asm-support.S: Add Mach-O variant.
> * gcc.target/x86_64/abi/bf16/m256bf16/asm-support.S: Likewise.
> * gcc.target/x86_64/abi/bf16/m512bf16/asm-support.S: Likewise.
Please note that in other directories asm-support-darwin.s is
introduced and included via .exp file. Is there a reason a different
approach is introduced here?
Uros.
next prev parent reply other threads:[~2022-12-05 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 11:51 Iain Sandoe
2022-12-04 20:20 ` Uros Bizjak
2022-12-04 20:30 ` Iain Sandoe
2022-12-05 10:37 ` Uros Bizjak [this message]
2022-12-05 14:54 ` Iain Sandoe
2022-12-05 21:07 ` Uros Bizjak
2022-12-05 21:17 ` Iain Sandoe
2022-12-05 21:22 ` 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='CAFULd4Y_O0v5zx=2jytyw5EuMWArF=tAgfH0qCXs6WK4dzkQzQ@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
/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).