gm2
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A beginner's question


From: Gaius Mulley
Subject: Re: A beginner's question
Date: Fri, 14 Apr 2023 13:56:32 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)

Rudolf Schubert <rudolf@muc.de> writes:

Hi Rudolf,

> The bad news is that my 'big' programm shows an internal compiler error.
> It goes like this:
>
> rudolf@debian: 
> /mnt/hgfs/mo1/lfs50_von_20190312/home/rudolf/lern/gpm_gm2/squash1/wrk_gm2_02 
> $ ./mach_squash1
> cc -c unix.c
> gm2 -fiso -c Ctv2.mod
> gm2 -fiso -fsoft-check-all squash1.mod Ctv2.o unix.o -o squash1 -lc -lcrypt 
> -lm
> terminate called after throwing an instance of 'unsigned int'
> *** WARNING *** there are active plugins, do not report this as a bug unless 
> you can reproduce it without enabling any plugins.
> Event                            | Plugins
> PLUGIN_FINISH                    | m2rte
> In function ‘welche_tabelle’:
> cc1gm2: internal compiler error: Abgebrochen
> 0xea857f crash_signal
>         ../../gcc-read-write/gcc/toplev.cc:314
> 0x7fe53b8a89ba __gnu_cxx::__verbose_terminate_handler()
>         ../../../../gcc-read-write/libstdc++-v3/libsupc++/vterminate.cc:95
> 0x7fe53b8b7f79 __cxxabiv1::__terminate(void (*)())
>         ../../../../gcc-read-write/libstdc++-v3/libsupc++/eh_terminate.cc:48
> 0x7fe53b8b7fe4 std::terminate()
>         ../../../../gcc-read-write/libstdc++-v3/libsupc++/eh_terminate.cc:58
> 0x7fe53b8b8236 __cxa_throw
>         ../../../../gcc-read-write/libstdc++-v3/libsupc++/eh_throw.cc:98
> 0x9951b6 InvokeHandler
>         m2/gm2-libs-boot/RTExceptions.c:484
> 0x9951b6 RTExceptions_Raise
>         m2/gm2-libs-boot/RTExceptions.c:946
> 0x995278 invalidloc
>         m2/gm2-libs-boot/RTExceptions.c:755
> 0x8cd7b6 contains_struct_check(tree_node*, tree_node_structure_enum, char 
> const*, int, char const*)
>         ../../gcc-read-write/gcc/tree.h:3653
> 0x8cd7b6 m2statement_BuildAssignmentTree
>         ../../gcc-read-write/gcc/m2/gm2-gcc/m2statement.cc:169
> 0x90898d CodeBecomes
>         m2/gm2-compiler-boot/M2GenGCC.c:4428
> 0x908ef8 CodeStatement
>         m2/gm2-compiler-boot/M2GenGCC.c:1756
> 0x90aea6 M2GenGCC_ConvertQuadsToTree
>         m2/gm2-compiler-boot/M2GenGCC.c:8449
> 0x933bba M2Scope_ForeachScopeBlockDo
>         m2/gm2-compiler-boot/M2Scope.c:661
> 0x8f1fc4 M2Code_CodeBlock
>         m2/gm2-compiler-boot/M2Code.c:512
> 0x8e013a Lists_ForeachItemInListDo
>         m2/gm2-compiler-boot/Lists.c:394
> 0x8f20d6 M2Code_CodeBlock
>         m2/gm2-compiler-boot/M2Code.c:544
> 0x8f247a DoCodeBlock
>         m2/gm2-compiler-boot/M2Code.c:271
> 0x8f247a M2Code_Code
>         m2/gm2-compiler-boot/M2Code.c:475
> x8f32b1 Compile
>         m2/gm2-compiler-boot/M2Comp.c:223
> Please submit a full bug report, with preprocessed source (by using 
> -freport-bug).
> Please include the complete backtrace with any bug report.
> See <https://gcc.gnu.org/bugs/> for instructions.
>
>
> The question now is how we should best proceed here. I think playing some
> ping pong between us is a waste of time. Therefore I make a proposal to you:
>
> If you do not laugh too loud about my programm I can send you all files
> so you may do with them what you want. I've put them on my page anyway
> and I don't care what people are doing with them. They might even port
> the software to GM2;-) Although it looks like MODULA code it's not very
> MODULAr because I packed everything into mainly one mod-file.  Well a
> little ctv-file (constants, types, variables) is also there and a small
> C-Interface. GPM did not know much about signals at the time I wrote
> this thing.

This would be really useful - many thanks - it would be much easier to
fix the ICE above.  Having different test code bases is extremely
valuable for stressing the compiler.  Feel free to email me a tarball
:-) of the code,

> BTW, concerning C-Interface I might also need some 'further training'. I
> did not quite get how parameter passing is working with open arrays 
> 'normally'.
> I'm using '...' mainly because there I found my parameters easily.
> Specifically I could not find the HIGH value. It seemed that just
> ramdom values were there. But this is another story we could talk about
> another time.

sound interesting,

regards,
Gaius




reply via email to

[Prev in Thread] Current Thread [Next in Thread]