public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/114907] __trunchfbf2 should be renamed to __extendhfbf2
Date: Mon, 06 May 2024 14:08:17 +0000	[thread overview]
Message-ID: <bug-114907-4-2WNpD61pF3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114907-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 58108
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58108&action=edit
gcc15-pr114907.patch

In retrospect, it has been a mistake to export __trunchfbf2 rather than
__extendhfbf2, but we've done that already.
Given that it is an arbitrary name choice (both are wrong), I think it is
better to change what gcc emits rather than what functions libgcc exports,
because we can backport what gcc emits but can't the libgcc changes.

  parent reply	other threads:[~2024-05-06 14:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
2024-05-01 14:29 ` [Bug libgcc/114907] " hjl.tools at gmail dot com
2024-05-01 14:29 ` hjl.tools at gmail dot com
2024-05-01 14:34 ` hjl.tools at gmail dot com
2024-05-01 14:49 ` [Bug libgcc/114907] __trunchfbf2 should be renamed to __extendhfbf2 hjl.tools at gmail dot com
2024-05-01 16:50 ` hjl.tools at gmail dot com
2024-05-01 16:58 ` hjl.tools at gmail dot com
2024-05-01 18:17 ` jakub at gcc dot gnu.org
2024-05-05  8:31 ` liuhongt at gcc dot gnu.org
2024-05-06 14:08 ` jakub at gcc dot gnu.org [this message]
2024-05-07 19:30 ` [Bug middle-end/114907] " cvs-commit at gcc dot gnu.org
2024-05-07 19:31 ` cvs-commit at gcc dot gnu.org
2024-05-07 19:33 ` jakub at gcc dot gnu.org
2024-05-09  4:26 ` cvs-commit at gcc dot gnu.org
2024-05-09  8:18 ` jakub 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-114907-4-2WNpD61pF3@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).