public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/101002] Some powerpc tests fail with -mlong-double-64
Date: Wed, 21 Jun 2023 23:19:21 +0000	[thread overview]
Message-ID: <bug-101002-4-FVhvfzkl77@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101002-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #4)
> These die because the struct we're using to check the alignment of uses long
> double as the "big" aligned type.  We could either disable the tests using a
> "dg-require-effective-target longdouble128" or we could use a different more
> aligned type in the struct.  Maybe _Float128 or _Decimal128 or use an
> attribute aligned?   Thoughts?

Maybe just some vector type?  Those have 128-bit alignment even with
-mno-altivec,
right?

> gcc.target/powerpc/pr85657-3.c
> gcc.target/powerpc/signbit-1.c
> pr85657-3.c:38:20: error: unknown type name ‘__ibm128’; did you mean
> ‘__int128’?
> 
> These die because we don't create the type __ibm128 when using
> -mlong-double-64, which seems strange since we do create the __float128 type
> used in the test cases.
> 
> Mike, I assume the __ibm128 type should always be created?

It always should, yes.  Always.  Unconditionally.

  parent reply	other threads:[~2023-06-21 23:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 20:18 [Bug testsuite/101002] New: " meissner at gcc dot gnu.org
2021-06-10 15:17 ` [Bug testsuite/101002] " bergner at gcc dot gnu.org
2021-06-11 20:54 ` segher at gcc dot gnu.org
2021-06-11 20:55 ` segher at gcc dot gnu.org
2023-06-20 21:20 ` bergner at gcc dot gnu.org
2023-06-21 17:30 ` bergner at gcc dot gnu.org
2023-06-21 17:41 ` bergner at gcc dot gnu.org
2023-06-21 20:31 ` bergner at gcc dot gnu.org
2023-06-21 20:34 ` bergner at gcc dot gnu.org
2023-06-21 23:19 ` segher at gcc dot gnu.org [this message]
2023-06-22 13:49 ` dje 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-101002-4-FVhvfzkl77@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).