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] New: LoongArch: Wrong code -with -mlsx -fno-fp-int-builtin-inexact Date: Fri, 17 Nov 2023 00:29:41 +0000 [thread overview] Message-ID: <bug-112578-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112578 Bug ID: 112578 Summary: LoongArch: Wrong code -with -mlsx -fno-fp-int-builtin-inexact Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: xry111 at gcc dot gnu.org Target Milestone: --- $ cat t.c #include <assert.h> #include <fenv.h> float f[4] = { 11.4, 5.14, 19.19, 8.10 }; int main() { for (int i = 0; i < 4; i++) f[i] = __builtin_floorf (f[i]); assert (!fetestexcept (FE_INEXACT)); } $ cc t.c -O2 -lm -fno-fp-int-builtin-inexact -mlsx $ ./a.out a.out: t.c:11: main: Assertion `!fetestexcept (FE_INEXACT)' failed. Aborted (core dumped)
next reply other threads:[~2023-11-17 0:29 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-17 0:29 xry111 at gcc dot gnu.org [this message] 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 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@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: linkBe 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).