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/105359] _Float128 expanders and builtins disabled on ppc targets with 64-bit long double
Date: Thu, 23 May 2024 06:24:39 +0000	[thread overview]
Message-ID: <bug-105359-4-lNdn6o3gp4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105359-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Alexandre Oliva <aoliva@gcc.gnu.org>:

https://gcc.gnu.org/g:dbdddc92a3b955fce71af47755c226132559eda2

commit r15-786-gdbdddc92a3b955fce71af47755c226132559eda2
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu May 23 03:20:19 2024 -0300

    [testsuite] xfail pr79004 on longdouble64; drop long_double_64bit

    Some of the asm opcodes expected by pr79004 depend on
    -mlong-double-128 to be output.  E.g., without this flag, the
    conditions of patterns @extenddf<mode>2 and extendsf<mode>2 do not
    hold, and so GCC resorts to libcalls instead of even trying
    rs6000_expand_float128_convert.

    Perhaps the conditions are too strict, and they could enable the use
    of conversion insns involving __ieee128/_Float128 even with 64-bit
    long doubles.

    For now, xfail the opcodes that are not available on longdouble64.

    While at that, drop long_double_64bit, since it's broken and sort of
    redundant.


    for  gcc/testsuite/ChangeLog

            PR target/105359
            * gcc.target/powerpc/pr79004.c: Xfail opcodes not available on
            longdouble64.
            * lib/target-supports.exp
            (check_effective_target_long_double_64bit): Drop.
            (add_options_for_long_double_64bit): Likewise.

      parent reply	other threads:[~2024-05-23  6:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-23 13:49 [Bug target/105359] New: " aoliva at gcc dot gnu.org
2022-04-27  5:24 ` [Bug target/105359] " aoliva at gcc dot gnu.org
2024-04-23  9:13 ` linkw at gcc dot gnu.org
2024-05-23  6:24 ` cvs-commit at gcc dot gnu.org [this message]

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-105359-4-lNdn6o3gp4@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).