From vvm at tut.by Tue Oct 4 11:10:26 2022 From: vvm at tut.by (vvm at tut.by) Date: Tue, 04 Oct 2022 12:10:26 +0300 Subject: [M3devel] Discussions #1095 ( branch zcxh, zero cost exception handling) AMD64_LINUX GCC and llvm backends with M3_USE_STACK_WALKER define Re: cm3/discussions/1095 In-Reply-To: <23161661504441@mail.yandex.by> References: <23161661504441@mail.yandex.by> Message-ID: <3519431664874369@mail.yandex.by> An HTML attachment was scrubbed... URL: From vvm at tut.by Tue Oct 11 12:53:47 2022 From: vvm at tut.by (vvm at tut.by) Date: Tue, 11 Oct 2022 13:53:47 +0300 Subject: [M3devel] cm3/tree/rodney-new Re: cm3/releases/tag/d5.11.9-ZZYYXX-20220208_13-48 In-Reply-To: <3519431664874369@mail.yandex.by> References: <23161661504441@mail.yandex.by> <3519431664874369@mail.yandex.by> Message-ID: <1893441665485041@mail.yandex.by> An HTML attachment was scrubbed... URL: From rodney.bates at gmx.com Thu Oct 27 19:38:43 2022 From: rodney.bates at gmx.com (Rodney Bates) Date: Thu, 27 Oct 2022 12:38:43 -0500 Subject: [M3devel] M3CG_LLVM.m3 Message-ID: OK, I got github master down and rebased my local branch onto it. Now when I try to push my local branch to my github branch, I get merge conflicts in M3CG_LLVM.m3.? I have not touched this file in many months and can't imagine how the version in github rodney-new would have ever gotten anything that didn't come from github master. But I can't make sense of the merged file anyway.? It seems to show differences where neither version to be merged agrees with what is in github master. Can I must assume github master is what is latest and copy it in to my local, as so-called manual resolve.? The problem stuff is from "Rationalize allocate temp" commit. From rodney.bates at gmx.com Sat Oct 29 17:54:55 2022 From: rodney.bates at gmx.com (Rodney Bates) Date: Sat, 29 Oct 2022 10:54:55 -0500 Subject: [M3devel] My changes merged, won't build on gcc Message-ID: The merge of my changes with the master branch are now pushed to github in branch rodney-new.? It fails to build with the gcc back end with: cm3cg: fatal error: *** bad M3CG version stamp (0x110), expected 0x120 It builds for me locally, and front group recompiles itself twice. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayk123 at hotmail.com Sat Oct 29 19:51:31 2022 From: jayk123 at hotmail.com (Jay K) Date: Sat, 29 Oct 2022 17:51:31 +0000 Subject: [M3devel] My changes merged, won't build on gcc In-Reply-To: References: Message-ID: Unfortunately the CI is not written quite correctly so this is "normal". It isn't written to accomodate changes to the cm3/gcc interchange format. It isn't very wrong, just slightly. - Jay ________________________________ From: M3devel on behalf of Rodney Bates Sent: Saturday, October 29, 2022 3:54 PM To: m3devel ; modula3/cm3 ; Rodney Bates Subject: [M3devel] My changes merged, won't build on gcc The merge of my changes with the master branch are now pushed to github in branch rodney-new. It fails to build with the gcc back end with: cm3cg: fatal error: *** bad M3CG version stamp (0x110), expected 0x120 It builds for me locally, and front group recompiles itself twice. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vvm at tut.by Sat Oct 29 21:14:08 2022 From: vvm at tut.by (vvm at tut.by) Date: Sat, 29 Oct 2022 22:14:08 +0300 Subject: [M3devel] My changes merged, won't build on gcc In-Reply-To: References: Message-ID: <598551667070682@mail.yandex.by> An HTML attachment was scrubbed... URL: From rodney.bates at gmx.com Sat Oct 29 23:43:35 2022 From: rodney.bates at gmx.com (Rodney Bates) Date: Sat, 29 Oct 2022 16:43:35 -0500 Subject: [M3devel] My changes merged, won't build on gcc In-Reply-To: <598551667070682@mail.yandex.by> References: <598551667070682@mail.yandex.by> Message-ID: <4478a975-f8ff-4b6e-7212-de565b7bc746@gmx.com> On 10/29/22 14:14, vvm at tut.by wrote: > + coder5506@, peter.mckinna@ > Hi! > > > CI/CD has been fixed ( in fact there is upgraded bootstrap used in Github Actions runner) two weeks ago > So is the broken version being triggered by a push to rodney-new branch? > > Beat regards, Victor Miasnikov > > 29.10.2022, 20:51, "Jay K" : > > Unfortunately the CI is not written /quite /correctly so this is "normal". > It isn't written to accomodate changes to the cm3/gcc interchange format. > It isn't very wrong, just slightly. > > ? - Jay > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > *From:* M3devel on behalf of Rodney Bates > *Sent:* Saturday, October 29, 2022 3:54 PM > *To:* m3devel ; modula3/cm3 ; Rodney Bates > *Subject:* [M3devel] My changes merged, won't build on gcc > The merge of my changes with the master branch are now pushed to > github in branch rodney-new.? It fails to build with the gcc back > end with: > > cm3cg: fatal error: *** bad M3CG version stamp (0x110), expected 0x120 > > It builds for me locally, and front group recompiles itself twice. > > > , > > _______________________________________________ > M3devel mailing list > M3devel at elegosoft.com > https://m3lists.elegosoft.com/mailman/listinfo/m3devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vvm at tut.by Sun Oct 30 07:10:43 2022 From: vvm at tut.by (vvm at tut.by) Date: Sun, 30 Oct 2022 09:10:43 +0300 Subject: [M3devel] My changes merged, won't build on gcc In-Reply-To: <4478a975-f8ff-4b6e-7212-de565b7bc746@gmx.com> References: <598551667070682@mail.yandex.by> <4478a975-f8ff-4b6e-7212-de565b7bc746@gmx.com> Message-ID: <2153041667109202@mail.yandex.by> An HTML attachment was scrubbed... URL: