public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/108956] [13 regression] SEGV in M2RTS_RegisterModule
Date: Tue, 28 Feb 2023 08:36:37 +0000 [thread overview]
Message-ID: <bug-108956-4-D15fyP2sDD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108956-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108956
--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #2 from Gaius Mulley <gaius at gcc dot gnu.org> ---
> The hand built modules were not changed to include the libname. (UnixArgs,
> ldtoa, dtoa for the tool pge). The patch corrects the hand built modules and
> also includes fixes for the attribute noreturn warnings generated when
> compiling M2RTS.cc.
Unfortunately, this didn't help: the SEGV and caller/callee mismatch
remain exactly the same.
next prev parent reply other threads:[~2023-02-28 8:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 21:26 [Bug modula2/108956] New: " ro at gcc dot gnu.org
2023-02-27 21:27 ` [Bug modula2/108956] " ro at gcc dot gnu.org
2023-02-28 1:15 ` gaius at gcc dot gnu.org
2023-02-28 1:16 ` gaius at gcc dot gnu.org
2023-02-28 1:29 ` gaius at gcc dot gnu.org
2023-02-28 8:36 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2023-02-28 13:02 ` gaius at gcc dot gnu.org
2023-02-28 15:36 ` cvs-commit at gcc dot gnu.org
2023-03-01 10:36 ` gaius at gcc dot gnu.org
2023-03-01 10:37 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-01 14:20 ` 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-108956-4-D15fyP2sDD@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).