public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106831] [13 Regression] mpfr-4.1.0 started failing 2 tests: tget_set_d64 and tget_set_d128 Date: Mon, 05 Sep 2022 12:57:36 +0000 [thread overview] Message-ID: <bug-106831-4-ot4K0fDmcr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106831-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106831 Aldy Hernandez <aldyh at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-09-05 Status|RESOLVED |NEW Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #4 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- reproduced on x86-64. Will take a look. Sorry for closing it prematurely.
next prev parent reply other threads:[~2022-09-05 12:57 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-05 7:18 [Bug target/106831] New: " slyfox at gcc dot gnu.org 2022-09-05 7:55 ` [Bug target/106831] " jakub at gcc dot gnu.org 2022-09-05 8:02 ` aldyh at gcc dot gnu.org 2022-09-05 8:04 ` aldyh at gcc dot gnu.org 2022-09-05 12:05 ` slyfox at gcc dot gnu.org 2022-09-05 12:57 ` aldyh at gcc dot gnu.org [this message] 2022-09-05 13:05 ` jakub at gcc dot gnu.org 2022-09-05 13:35 ` aldyh at gcc dot gnu.org 2022-09-05 13:48 ` [Bug middle-end/106831] " jakub at gcc dot gnu.org 2022-09-05 13:54 ` aldyh at gcc dot gnu.org 2022-09-05 14:56 ` jakub at gcc dot gnu.org 2022-09-05 15:57 ` cvs-commit at gcc dot gnu.org 2022-09-05 15:59 ` aldyh at gcc dot gnu.org 2022-09-05 19:32 ` joseph at codesourcery dot com 2022-09-18 7:04 ` cvs-commit 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-106831-4-ot4K0fDmcr@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).