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/101392] cc1gm2 -fdump-system-exports SEGV on Solaris/SPARC Date: Thu, 10 Nov 2022 13:01:21 +0000 [thread overview] Message-ID: <bug-101392-4-BkPzSwlT1j@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101392-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101392 --- Comment #6 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #5 from Gaius Mulley <gaius at gcc dot gnu.org> --- > thanks for this excellent analysis. Here is a patch which will fix the passing > of binop.proc in M2GenGCC.c. I'd tried looking into this at least once before, but didn't get anywhere then. > diff --git a/gcc/m2/gm2-gcc/m2expr.def b/gcc/m2/gm2-gcc/m2expr.def > index 8988c78d575..e622d31d09b 100644 > --- a/gcc/m2/gm2-gcc/m2expr.def > +++ b/gcc/m2/gm2-gcc/m2expr.def > @@ -19,7 +19,7 @@ You should have received a copy of the GNU General Public > License > along with GNU Modula-2; see the file COPYING3. If not see > <http://www.gnu.org/licenses/>. *) > > -DEFINITION MODULE m2expr ; > +DEFINITION MODULE FOR "C" m2expr ; > > FROM SYSTEM IMPORT ADDRESS ; > FROM m2tree IMPORT Tree ; That worked like a charm and got the build way beyond the current failure point. I later ran into PR modula2/105392 again, but that proved to be a similar issue. Thanks a lot.
next prev parent reply other threads:[~2022-11-10 13:01 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-09 12:34 [Bug modula2/101392] New: " ro at gcc dot gnu.org 2021-09-14 10:15 ` [Bug modula2/101392] " ro at gcc dot gnu.org 2022-05-03 15:27 ` gaius at gcc dot gnu.org 2022-05-04 13:18 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-11-07 13:15 ` ro at gcc dot gnu.org 2022-11-09 16:30 ` gaius at gcc dot gnu.org 2022-11-10 13:01 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2022-11-11 10:50 ` 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-101392-4-BkPzSwlT1j@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).