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

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

            Bug ID: 107604
           Summary: FAIL: gcc.target/aarch64/aapcs64/test_dfp_17.c
                    execution,  -O0  fails on aarch64_be
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: ABI, testsuite-fail, wrong-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---
            Target: aarch64_be-linux-gnu

FAIL: gcc.target/aarch64/aapcs64/test_dfp_17.c execution,  -O0 
FAIL: gcc.target/aarch64/aapcs64/test_dfp_17.c execution,  -O1 
FAIL: gcc.target/aarch64/aapcs64/test_dfp_17.c execution,  -O2 
FAIL: gcc.target/aarch64/aapcs64/test_dfp_17.c execution,  -O3 -g 
FAIL: gcc.target/aarch64/aapcs64/test_dfp_17.c execution,  -Os 
FAIL: gcc.target/aarch64/aapcs64/test_dfp_17.c execution,  -Og -g 

My bet is there is mistmatch between the caller and callee; one side takes into
account big vs little endian shifting while the other side does not ...

             reply	other threads:[~2022-11-10  6:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  6:30 pinskia at gcc dot gnu.org [this message]
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
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@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).