public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/109125] [13 regression] SIGBUS in m2pim_ldtoa_ldtoa
Date: Tue, 14 Mar 2023 19:55:11 +0000 [thread overview]
Message-ID: <bug-109125-4-PtcMTIImMU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109125-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109125
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Gaius Mulley <gaius@gcc.gnu.org>:
https://gcc.gnu.org/g:19c5dfc29d83101e415590e778b99e7c37d9b730
commit r13-6671-g19c5dfc29d83101e415590e778b99e7c37d9b730
Author: Gaius Mulley <gaiusmod2@gmail.com>
Date: Tue Mar 14 19:52:11 2023 +0000
PR 109125 Modula2 SIGBUS in m2pim_ldtoa_ldtoa
13 regression failures seen on sparc SIGBUS in m2pim_ldtoa_ldtoa.
This patch fixes int bool parameter mismatches between the
definition modules and their C/C++ implementations.
gcc/m2/ChangeLog:
PR modula2/109125
* gm2-libs-ch/cgetopt.c (cgetopt_SetOption): Replace int
for bool.
* gm2-libs-ch/termios.c (doSetUnset): Replace int for bool.
* gm2-libs/Builtins.mod (isfinitef): Correct typo in return
statement.
libgm2/ChangeLog:
PR modula2/109125
* libm2iso/ErrnoCategory.cc (FALSE): Remove.
(TRUE): Remove.
* libm2iso/wrapsock.c (TRUE): Remove.
(FALSE): Remove.
* libm2iso/wraptime.cc (TRUE): Remove.
(FALSE): Remove.
* libm2pim/cgetopt.cc: Replace int for bool for every BOOLEAN
parameter in the definition module.
* libm2pim/dtoa.cc: Ditto.
* libm2pim/ldtoa.cc: Ditto.
* libm2pim/termios.cc: Ditto.
(doSetUnset): Replace int for bool.
Signed-off-by: Gaius Mulley <gaiusmod2@gmail.com>
next prev parent reply other threads:[~2023-03-14 19:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 10:08 [Bug modula2/109125] New: " ro at gcc dot gnu.org
2023-03-14 10:08 ` [Bug modula2/109125] " ro at gcc dot gnu.org
2023-03-14 16:41 ` gaius at gcc dot gnu.org
2023-03-14 17:25 ` gaius at gcc dot gnu.org
2023-03-14 17:27 ` gaius at gcc dot gnu.org
2023-03-14 19:55 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-15 9:05 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-15 13:53 ` gaius at gcc dot gnu.org
2023-03-15 14:00 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-15 14:23 ` rguenth at gcc dot gnu.org
2023-03-15 20:09 ` gaius at gcc dot gnu.org
2023-03-15 21:31 ` cvs-commit at gcc dot gnu.org
2023-03-16 14:43 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-16 20:42 ` cvs-commit at gcc dot gnu.org
2023-03-21 10:32 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-21 18:26 ` 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-109125-4-PtcMTIImMU@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).