public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107604] FAIL: gcc.target/aarch64/aapcs64/test_dfp_17.c execution,  -O0  fails on aarch64_be
Date: Tue, 22 Nov 2022 13:10:08 +0000	[thread overview]
Message-ID: <bug-107604-4-BwOAVQo9Pe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107604-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107604

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Christophe Lyon <clyon@gcc.gnu.org>:

https://gcc.gnu.org/g:4eb3a48698b2ca43967a4e7e7cfc0408192e85b2

commit r13-4235-g4eb3a48698b2ca43967a4e7e7cfc0408192e85b2
Author: Christophe Lyon <christophe.lyon@arm.com>
Date:   Tue Nov 22 08:33:06 2022 +0000

    aarch64: Fix test_dfp_17.c for big-endian [PR 107604]

    gcc.target/aarch64/aapcs64/test_dfp_17.c has been failing on
    big-endian, because the _Decimal32 on-stack argument is not padded in
    the same direction depending on endianness.

    This patch fixes the testcase so that it expects the argument in the
    right stack location, similarly to what other tests do in the same
    directory.

    gcc/testsuite/ChangeLog:

            PR target/107604
            * gcc.target/aarch64/aapcs64/test_dfp_17.c: Fix for big-endian.

  parent reply	other threads:[~2022-11-22 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  6:30 [Bug target/107604] New: " pinskia at gcc dot gnu.org
2022-11-10 15:53 ` [Bug target/107604] " clyon at gcc dot gnu.org
2022-11-17 14:00 ` clyon at gcc dot gnu.org
2022-11-17 16:39 ` clyon at gcc dot gnu.org
2022-11-22 13:10 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-22 13:15 ` clyon at gcc dot gnu.org
2022-11-28 22:38 ` pinskia at gcc dot gnu.org

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=bug-107604-4-BwOAVQo9Pe@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).