public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/109379] New: improve __builtin_fmal
@ 2023-04-02 21:12 g.peterhoff@t-online.de
  2023-04-02 21:21 ` [Bug target/109379] " pinskia at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: g.peterhoff@t-online.de @ 2023-04-02 21:12 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 109379
           Summary: improve __builtin_fmal
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: g.peterhoff@t-online.de
  Target Milestone: ---

Hello gcc team,
__builtin_fmal generates quite a lot of overhead. Can you please optimize this
or make it an inline function?

thx
Gero

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug target/109379] improve __builtin_fmal
  2023-04-02 21:12 [Bug c++/109379] New: improve __builtin_fmal g.peterhoff@t-online.de
@ 2023-04-02 21:21 ` pinskia at gcc dot gnu.org
  2023-04-02 21:21 ` pinskia at gcc dot gnu.org
  2023-04-02 21:22 ` pinskia at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-02 21:21 UTC (permalink / raw)
  To: gcc-bugs

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
There is no way to improve fmal really. Because it requires to do the multiple
and add in infinite precision and only doing the rounding afterwards.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug target/109379] improve __builtin_fmal
  2023-04-02 21:12 [Bug c++/109379] New: improve __builtin_fmal g.peterhoff@t-online.de
  2023-04-02 21:21 ` [Bug target/109379] " pinskia at gcc dot gnu.org
@ 2023-04-02 21:21 ` pinskia at gcc dot gnu.org
  2023-04-02 21:22 ` pinskia at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-02 21:21 UTC (permalink / raw)
  To: gcc-bugs

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WONTFIX                     |INVALID

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug target/109379] improve __builtin_fmal
  2023-04-02 21:12 [Bug c++/109379] New: improve __builtin_fmal g.peterhoff@t-online.de
  2023-04-02 21:21 ` [Bug target/109379] " pinskia at gcc dot gnu.org
  2023-04-02 21:21 ` pinskia at gcc dot gnu.org
@ 2023-04-02 21:22 ` pinskia at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-02 21:22 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
and doing it inline is not going to help that much as the overhead is not due
to not being inlined; it is just an expensive operation as it has to be done
using soft-float.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-04-02 21:22 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-04-02 21:12 [Bug c++/109379] New: improve __builtin_fmal g.peterhoff@t-online.de
2023-04-02 21:21 ` [Bug target/109379] " pinskia at gcc dot gnu.org
2023-04-02 21:21 ` pinskia at gcc dot gnu.org
2023-04-02 21:22 ` pinskia at gcc dot gnu.org

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).