public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112578] LoongArch: Wrong code -with -mlsx -fno-fp-int-builtin-inexact
Date: Mon, 20 Nov 2023 00:51:04 +0000 [thread overview]
Message-ID: <bug-112578-4-A3sF2jEEUR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112578-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112578
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
URL|https://gcc.gnu.org/piperma |https://gcc.gnu.org/piperma
|il/gcc-patches/2023-Novembe |il/gcc-patches/2023-Novembe
|r/637097.html |r/637316.html
See Also|https://github.com/loongson |
|-community/discussions/issu |
|es/7 |
--- Comment #4 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Xi Ruoyao from comment #3)
> https://gcc.gnu.org/pipermail/gcc-patches/2023-November/637097.html
>
> This fixes most of -ml[a]sx -fno-fp-int-builtin-inexact issues on LoongArch,
> except PR107723.
Updated: https://gcc.gnu.org/pipermail/gcc-patches/2023-November/637316.html
next prev parent reply other threads:[~2023-11-20 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 0:29 [Bug target/112578] New: " xry111 at gcc dot gnu.org
2023-11-17 11:18 ` [Bug target/112578] " xry111 at gcc dot gnu.org
2023-11-17 11:31 ` chenglulu at loongson dot cn
2023-11-17 20:54 ` xry111 at gcc dot gnu.org
2023-11-20 0:51 ` xry111 at gcc dot gnu.org [this message]
2023-11-29 7:07 ` cvs-commit at gcc dot gnu.org
2023-11-29 7:09 ` xry111 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-112578-4-A3sF2jEEUR@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).