public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/97142] __builtin_fmod not optimized on POWER
Date: Tue, 07 Sep 2021 17:58:25 +0000	[thread overview]
Message-ID: <bug-97142-4-vE0ybWPv3Z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97142-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #17 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to CVS Commits from comment #16)
> The master branch has been updated by Xiong Hu Luo <luoxhu@gcc.gnu.org>:

So fixed on trunk.

The Version about is to 10.2, does that mean we're going to back port this to
the release branches, or are we calling it good with trunk?

  parent reply	other threads:[~2021-09-07 17:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21 10:57 [Bug target/97142] New: " fx at gnu dot org
2020-09-21 11:24 ` [Bug target/97142] " rguenth at gcc dot gnu.org
2020-09-21 11:26 ` rguenth at gcc dot gnu.org
2020-09-21 14:42 ` bergner at gcc dot gnu.org
2020-09-21 14:45 ` fx at gnu dot org
2020-09-21 14:47 ` fx at gnu dot org
2020-09-21 17:52 ` segher at gcc dot gnu.org
2020-09-21 18:10 ` bergner at gcc dot gnu.org
2020-09-21 19:33 ` segher at gcc dot gnu.org
2020-09-21 21:54 ` bergner at gcc dot gnu.org
2021-04-13  6:24 ` luoxhu at gcc dot gnu.org
2021-04-13 16:26 ` segher at gcc dot gnu.org
2021-05-27  0:54 ` luoxhu at gcc dot gnu.org
2021-09-02 22:05 ` bergner at gcc dot gnu.org
2021-09-02 22:38 ` segher at gcc dot gnu.org
2021-09-03  2:33 ` luoxhu at gcc dot gnu.org
2021-09-07  1:29 ` cvs-commit at gcc dot gnu.org
2021-09-07 17:58 ` bergner at gcc dot gnu.org [this message]
2021-09-07 19:34 ` segher at gcc dot gnu.org
2021-09-07 21:20 ` segher at gcc dot gnu.org
2021-09-14  5:33 ` cvs-commit at gcc dot gnu.org
2021-09-14  5:34 ` cvs-commit at gcc dot gnu.org
2021-09-14  5:36 ` luoxhu 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-97142-4-vE0ybWPv3Z@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).