public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/105390] [12 regression] sigfpe redeclared in mc-boot-ch/GSysExceptions.c Date: Tue, 26 Apr 2022 10:47:07 +0000 [thread overview] Message-ID: <bug-105390-4-2dsoNwEpoV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105390-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105390 --- Comment #1 from Rainer Orth <ro at gcc dot gnu.org> --- Created attachment 52882 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52882&action=edit Hacky patch. I've only now noticed that the mechanical sigfpe -> sigfpe_ change shouldn't have been applied to sigfpeDespatcher, but I'm leaving the patch as is since that's what allowed the build to continue.
next prev parent reply other threads:[~2022-04-26 10:47 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-26 10:45 [Bug modula2/105390] New: " ro at gcc dot gnu.org 2022-04-26 10:47 ` ro at gcc dot gnu.org [this message] 2022-04-26 12:37 ` [Bug modula2/105390] " rguenth at gcc dot gnu.org 2022-04-29 10:06 ` [Bug modula2/105390] [12/13 " 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-105390-4-2dsoNwEpoV@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).