public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gaius at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/108143] LONGREAL and powerpc64le-linux Date: Tue, 19 Sep 2023 13:51:44 +0000 [thread overview] Message-ID: <bug-108143-4-I3WoJyZBWZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108143-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108143 Gaius Mulley <gaius at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #55773|0 |1 is obsolete| | Attachment #55917|0 |1 is obsolete| | --- Comment #11 from Gaius Mulley <gaius at gcc dot gnu.org> --- Created attachment 55933 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55933&action=edit Proposed fix after cleanup Here is the patch after a cleanup and further fixes. Bootstrapped on raspian 32 armv7 (12 failures), aarch64 (0 failures), x86_64 (0 failures), ppc64le (0 failures).
next prev parent reply other threads:[~2023-09-19 13:51 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-16 10:09 [Bug modula2/108143] New: " jakub at gcc dot gnu.org 2022-12-16 11:03 ` [Bug modula2/108143] " rguenth at gcc dot gnu.org 2022-12-16 11:07 ` jakub at gcc dot gnu.org 2022-12-16 15:08 ` gaius at gcc dot gnu.org 2022-12-16 15:46 ` segher at gcc dot gnu.org 2023-08-20 22:28 ` cvs-commit at gcc dot gnu.org 2023-08-21 23:16 ` gaius at gcc dot gnu.org 2023-08-21 23:17 ` gaius at gcc dot gnu.org 2023-08-22 0:05 ` gaius at gcc dot gnu.org 2023-08-22 3:46 ` gaius at gcc dot gnu.org 2023-09-17 18:35 ` gaius at gcc dot gnu.org 2023-09-19 13:51 ` gaius at gcc dot gnu.org [this message] 2023-09-19 18:24 ` cvs-commit at gcc dot gnu.org 2023-09-19 18:35 ` gaius 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-108143-4-I3WoJyZBWZ@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).