public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/112506] gm2 test failures on x86_64-apple-darwin21
Date: Mon, 13 Nov 2023 07:25:49 +0000 [thread overview]
Message-ID: <bug-112506-4-15UlAEZkvj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112506-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112506
--- Comment #1 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
The stack trace for the "expecting a DefImp symbol" error is the following:
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 2.1
* frame #0: 0x000000010004a240
cc1gm2`::M2Emit_InternalError(message_="expecting a DefImp symbol",
_message_high=25) at M2Emit.c:97:8
frame #1: 0x000000010004be0c
cc1gm2`::M2Error_InternalError(message_=<unavailable>, _message_high=25) at
M2Error.c:2605:24
frame #2: 0x00000001000a9543 cc1gm2`::SymbolTable_IsDefinitionForC(Sym=165)
at SymbolTable.c:16397:31
frame #3: 0x0000000100047676 cc1gm2`::M2Comp_compile(void *) at
M2Comp.c:1114:43
frame #4: 0x00000001000475db cc1gm2`::M2Comp_compile(void *) at
M2Comp.c:1189:28
frame #5: 0x0000000100047246 cc1gm2`::M2Comp_compile(void *) [inlined]
Compile(s=0x00006000037079c0) at M2Comp.c:427:11
frame #6: 0x0000000100047246
cc1gm2`::M2Comp_compile(filename=<unavailable>) at M2Comp.c:1540:11
frame #7: 0x00000001000063e1 cc1gm2`::gm2_langhook_parse_file() at
gm2-lang.cc:803:26
frame #8: 0x0000000100006393 cc1gm2`::gm2_langhook_parse_file() at
gm2-lang.cc:810:25
frame #9: 0x0000000101476d04 cc1gm2`::compile_file() at toplev.cc:446:25
frame #10: 0x0000000101db1d06 cc1gm2`toplev::main(int, char**) at
toplev.cc:2129:24
frame #11: 0x0000000101dc13c0 cc1gm2
The trace for the other one is:
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
* frame #0: 0x00000001000692b0 cc1gm2`::M2MetaError_MetaErrorT1(tok=3628,
m_="module {%1Ea} has a corresponding DEFINITION MODULE but no IMPLEMENTATION
keyword in the main module", _m_high=100, s=155) at M2MetaError.c:3471:1
frame #1: 0x000000010009823d
cc1gm2`::P1SymBuild_P1StartBuildProgramModule() at P1SymBuild.c:633:31
frame #2: 0x00000001000e5b43 cc1gm2`::P1Build_CompilationUnit() [inlined]
ProgramModule(stopset0=1, stopset1=0, stopset2=0) at P1Build.c:3038:40
frame #3: 0x00000001000e5b10 cc1gm2`::P1Build_CompilationUnit() [inlined]
ImplementationOrProgramModule(stopset0=1, stopset1=0, stopset2=0) at
P1Build.c:3143:21
frame #4: 0x00000001000e5b10 cc1gm2`::P1Build_CompilationUnit() [inlined]
FileUnit(stopset0=1, stopset1=0, stopset2=0) at P1Build.c:2993:37
frame #5: 0x00000001000e51e0 cc1gm2`::P1Build_CompilationUnit() at
P1Build.c:6664:12
frame #6: 0x0000000100047c59 cc1gm2`::M2Comp_compile(void *) at
M2Comp.c:1258:46
frame #7: 0x0000000100047bd8 cc1gm2`::M2Comp_compile(void *) [inlined]
Compile(s=0x000060000370a1c0) at M2Comp.c:433:11
frame #8: 0x0000000100047246
cc1gm2`::M2Comp_compile(filename=<unavailable>) at M2Comp.c:1540:11
frame #9: 0x00000001000063e1 cc1gm2`::gm2_langhook_parse_file() at
gm2-lang.cc:803:26
frame #10: 0x0000000100006393 cc1gm2`::gm2_langhook_parse_file() at
gm2-lang.cc:810:25
frame #11: 0x0000000101476d04 cc1gm2`::compile_file() at toplev.cc:446:25
frame #12: 0x0000000101db1d06 cc1gm2`toplev::main(int, char**) at
toplev.cc:2129:24
frame #13: 0x0000000101dc13c0 cc1gm2
next prev parent reply other threads:[~2023-11-13 7:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 7:12 [Bug modula2/112506] New: " fxcoudert at gcc dot gnu.org
2023-11-13 7:13 ` [Bug modula2/112506] " fxcoudert at gcc dot gnu.org
2023-11-13 7:25 ` fxcoudert at gcc dot gnu.org [this message]
2023-11-20 16:19 ` iains at gcc dot gnu.org
2023-11-20 16:22 ` iains at gcc dot gnu.org
2023-11-22 22:32 ` gaius at gcc dot gnu.org
2024-01-27 11:36 ` iains at gcc dot gnu.org
2024-02-01 10:25 ` cvs-commit at gcc dot gnu.org
2024-02-01 10:55 ` gaius at gcc dot gnu.org
2024-02-01 10:57 ` iains at gcc dot gnu.org
2024-02-01 20:42 ` iains at gcc dot gnu.org
2024-02-02 9:46 ` 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-112506-4-15UlAEZkvj@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).