illegal recursive declaration crashes frontend #1109
Comments
|
Hmm, This works OK for me, using the compiler in branch rodney-new.
I was under the belief that everything in rodney-new was merged
and pushed into master on github. I'll look into getting things
merged.
By "works", I mean produces the compile error, but no segfault.
…On 10/17/22 21:05, peter mckinna wrote:
This code from e019
CONST
N = N + 1l;
causes a segv in the frontend from a stack overflow caused
(ironically) by infinite recursion between Expr.RepTypeOf
and AddExpr.RepTypeOf
similar segv for N - 1, N * 1, N DIV 1 but strangely
not N MOD 1
—
Reply to this email directly, view it on GitHub <#1109>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSVZNF6OOTS2NYHLPDBWVDWDYAVLANCNFSM6AAAAAARHTSKR4>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
No worries,
I have had merge problems of my own in the past.
While you are at it, have a look at e020. It compiles but crashes.
The stderr.pgm file suggests it should produce a runtime
error - invalid cycle in super types.
On Wed, 19 Oct 2022 at 10:07, Rodney M. Bates ***@***.***>
wrote:
… Hmm, This works OK for me, using the compiler in branch rodney-new.
I was under the belief that everything in rodney-new was merged
and pushed into master on github. I'll look into getting things
merged.
By "works", I mean produces the compile error, but no segfault.
On 10/17/22 21:05, peter mckinna wrote:
>
> This code from e019
> CONST
> N = N + 1l;
>
> causes a segv in the frontend from a stack overflow caused
> (ironically) by infinite recursion between Expr.RepTypeOf
> and AddExpr.RepTypeOf
> similar segv for N - 1, N * 1, N DIV 1 but strangely
> not N MOD 1
>
> —
> Reply to this email directly, view it on GitHub <
#1109>, or unsubscribe <
https://github.com/notifications/unsubscribe-auth/ABSVZNF6OOTS2NYHLPDBWVDWDYAVLANCNFSM6AAAAAARHTSKR4
>.
> You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#1109 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABALZX5YE3UUDLLVKYBHSWLWD4UTTANCNFSM6AAAAAARHTSKR4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
In short: please do it ( merge) Thank! |
|
( a-la P.S.
Why? "branch rodney-new" tested as part of 2-3 latest releases with good results. VictorMiasnikov@a5580bd ) |
I.e. before "merge branch rodney-new" we have: 844d77c https://github.com/modula3/cm3/actions/runs/3231157773 But after integration we have: |
I.e. before: After: P.S. This looks like changing "error message" text: |
|
P.P.S. https://github.com/VictorMiasnikov/cm3/actions/runs/3279987990/jobs/5400217924
https://github.com/VictorMiasnikov/cm3/actions/runs/3280163012/jobs/5400877203 AMD64_LINUX gcc P.P.P.S. "Combo branch": https://github.com/VictorMiasnikov/cm3/releases/tag/d5.11.9-ZZYYXX-20221019_15-00 |
|
OK, excuse my frustration, but once again, I can't seem to
get the most basic things done in git, despite a 300+ page
book, a 400+ page book, and lots of helpful emails from last fall.
All I am trying at this point is to get my local master branch
up to date with the github master branch. I have:
~/proj/m3/git-merge/cm3/master$ git remote -v
eric https://github.com/coder5506/cm3.git (fetch)
eric https://github.com/coder5506/cm3.git (push)
origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
origin /home/rodney/proj/m3/git-devel/cm3 (push)
upstream https://github.com/modula3/cm3.git (fetch)
upstream https://github.com/modula3/cm3.git (push)
and have done git fetch:
~/proj/m3/git-merge/cm3/master$ git remote -v
eric https://github.com/coder5506/cm3.git (fetch)
eric https://github.com/coder5506/cm3.git (push)
origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
origin /home/rodney/proj/m3/git-devel/cm3 (push)
upstream https://github.com/modula3/cm3.git (fetch)
upstream https://github.com/modula3/cm3.git (push)
***@***.***:~/proj/m3/git-merge/cm3/master$ git fetch upstream
remote: Enumerating objects: 615, done.
remote: Counting objects: 100% (614/614), done.
remote: Compressing objects: 100% (231/231), done.
remote: Total 615 (delta 373), reused 592 (delta 367), pack-reused 1
Receiving objects: 100% (615/615), 556.76 KiB | 1.66 MiB/s, done.
Resolving deltas: 100% (373/373), completed with 27 local objects.
From https://github.com/modula3/cm3
57ee5fe..65ca3e1 master -> upstream/master
* [new branch] zcxh -> upstream/zcxh
apparently successfully. so all the files of master on github
should be copied locally inside my .git, and my "remote"
(confusingly misnamed) named upstream should point to my
local copy of the latest github.master.head.
But:
~/proj/m3/git-merge/cm3/master$ git merge upstream/master
fatal: Not possible to fast-forward, aborting.
***@***.***:~/proj/m3/git-merge/cm3/master$ git merge upstream master
merge: upstream - not something we can merge
Previously, I remember discovering that some git
commands call for "upstream/master" and others "upstream master" to
name a (local copy of) a branch at a remote location, but I don't find
any reference material telling me which, particularly for git merge,
so I tried both. Looks like the slash was the right one, but why
does it refuse and what to do?
…On 10/18/22 21:17, peter mckinna wrote:
No worries,
I have had merge problems of my own in the past.
While you are at it, have a look at e020. It compiles but crashes.
The stderr.pgm file suggests it should produce a runtime
error - invalid cycle in super types.
|
|
PS:
1. I am quite sure this is the way I did this last time, some months ago.
2. I have definitely made no changes to my local master copy since then.
3. I pushed my rodney-new branch up to github, in case somebody has an
urgent need for its contents.
4. I added a bunch of cases to e019. All give compile errors, as expected
using my latest compiler, built from rodney-new, but don't crash. A
couple give a second, probably extraneous, compile message.
…On 10/24/22 15:01, Rodney Bates wrote:
OK, excuse my frustration, but once again, I can't seem to
get the most basic things done in git, despite a 300+ page
book, a 400+ page book, and lots of helpful emails from last fall.
All I am trying at this point is to get my local master branch
up to date with the github master branch. I have:
~/proj/m3/git-merge/cm3/master$ git remote -v
eric https://github.com/coder5506/cm3.git (fetch)
eric https://github.com/coder5506/cm3.git (push)
origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
origin /home/rodney/proj/m3/git-devel/cm3 (push)
upstream https://github.com/modula3/cm3.git (fetch)
upstream https://github.com/modula3/cm3.git (push)
and have done git fetch:
~/proj/m3/git-merge/cm3/master$ git remote -v
eric https://github.com/coder5506/cm3.git (fetch)
eric https://github.com/coder5506/cm3.git (push)
origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
origin /home/rodney/proj/m3/git-devel/cm3 (push)
upstream https://github.com/modula3/cm3.git (fetch)
upstream https://github.com/modula3/cm3.git (push)
***@***.***:~/proj/m3/git-merge/cm3/master$ git fetch upstream
remote: Enumerating objects: 615, done.
remote: Counting objects: 100% (614/614), done.
remote: Compressing objects: 100% (231/231), done.
remote: Total 615 (delta 373), reused 592 (delta 367), pack-reused 1
Receiving objects: 100% (615/615), 556.76 KiB | 1.66 MiB/s, done.
Resolving deltas: 100% (373/373), completed with 27 local objects.
From https://github.com/modula3/cm3
57ee5fe..65ca3e1 master -> upstream/master
* [new branch] zcxh -> upstream/zcxh
apparently successfully. so all the files of master on github
should be copied locally inside my .git, and my "remote"
(confusingly misnamed) named upstream should point to my
local copy of the latest github.master.head.
But:
~/proj/m3/git-merge/cm3/master$ git merge upstream/master
fatal: Not possible to fast-forward, aborting.
***@***.***:~/proj/m3/git-merge/cm3/master$ git merge upstream master
merge: upstream - not something we can merge
Previously, I remember discovering that some git
commands call for "upstream/master" and others "upstream master" to
name a (local copy of) a branch at a remote location, but I don't find
any reference material telling me which, particularly for git merge,
so I tried both. Looks like the slash was the right one, but why
does it refuse and what to do?
On 10/18/22 21:17, peter mckinna wrote:
> No worries,
>
> I have had merge problems of my own in the past.
> While you are at it, have a look at e020. It compiles but crashes.
> The stderr.pgm file suggests it should produce a runtime
> error - invalid cycle in super types.
>
|
|
Eric may have better solutions but I do the following.
If I have been making minor changes on master make sure you are on the
master branch
on your local machine.
git checkout master
git branch (to make sure)
git fetch
git pull --rebase origin master (rebase creates commits on your local
master so your changes are the latest - may provoke conflicts)
git push origin master (sends your local master to remote)
If I have created a local branch I merge on my local machine first then do
the push.
git checkout master (make sure you are on master locally)
git fetch
git pull --rebase origin master
git merge other-branch (may have conflicts gti tells you what to do)
git commit -a ( creates a merge commit)
git push origin master (or just git push works for me)
now master branch should be the same on local and remote.
git log (verify your commits are in place)
On Tue, 25 Oct 2022 at 07:30, Rodney M. Bates ***@***.***>
wrote:
… PS:
1. I am quite sure this is the way I did this last time, some months ago.
2. I have definitely made no changes to my local master copy since then.
3. I pushed my rodney-new branch up to github, in case somebody has an
urgent need for its contents.
4. I added a bunch of cases to e019. All give compile errors, as expected
using my latest compiler, built from rodney-new, but don't crash. A
couple give a second, probably extraneous, compile message.
On 10/24/22 15:01, Rodney Bates wrote:
> OK, excuse my frustration, but once again, I can't seem to
> get the most basic things done in git, despite a 300+ page
> book, a 400+ page book, and lots of helpful emails from last fall.
>
> All I am trying at this point is to get my local master branch
> up to date with the github master branch. I have:
>
> ~/proj/m3/git-merge/cm3/master$ git remote -v
> eric https://github.com/coder5506/cm3.git (fetch)
> eric https://github.com/coder5506/cm3.git (push)
> origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
> origin /home/rodney/proj/m3/git-devel/cm3 (push)
> upstream https://github.com/modula3/cm3.git (fetch)
> upstream https://github.com/modula3/cm3.git (push)
>
> and have done git fetch:
>
> ~/proj/m3/git-merge/cm3/master$ git remote -v
> eric https://github.com/coder5506/cm3.git (fetch)
> eric https://github.com/coder5506/cm3.git (push)
> origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
> origin /home/rodney/proj/m3/git-devel/cm3 (push)
> upstream https://github.com/modula3/cm3.git (fetch)
> upstream https://github.com/modula3/cm3.git (push)
> ***@***.***:~/proj/m3/git-merge/cm3/master$ git fetch upstream
> remote: Enumerating objects: 615, done.
> remote: Counting objects: 100% (614/614), done.
> remote: Compressing objects: 100% (231/231), done.
> remote: Total 615 (delta 373), reused 592 (delta 367), pack-reused 1
> Receiving objects: 100% (615/615), 556.76 KiB | 1.66 MiB/s, done.
> Resolving deltas: 100% (373/373), completed with 27 local objects.
> From https://github.com/modula3/cm3
> 57ee5fe..65ca3e1 master -> upstream/master
> * [new branch] zcxh -> upstream/zcxh
>
> apparently successfully. so all the files of master on github
> should be copied locally inside my .git, and my "remote"
> (confusingly misnamed) named upstream should point to my
> local copy of the latest github.master.head.
>
> But:
>
> ~/proj/m3/git-merge/cm3/master$ git merge upstream/master
> fatal: Not possible to fast-forward, aborting.
> ***@***.***:~/proj/m3/git-merge/cm3/master$ git merge upstream master
> merge: upstream - not something we can merge
>
>
> Previously, I remember discovering that some git
> commands call for "upstream/master" and others "upstream master" to
> name a (local copy of) a branch at a remote location, but I don't find
> any reference material telling me which, particularly for git merge,
> so I tried both. Looks like the slash was the right one, but why
> does it refuse and what to do?
>
>
> On 10/18/22 21:17, peter mckinna wrote:
>> No worries,
>>
>> I have had merge problems of my own in the past.
>> While you are at it, have a look at e020. It compiles but crashes.
>> The stderr.pgm file suggests it should produce a runtime
>> error - invalid cycle in super types.
>>
>
—
Reply to this email directly, view it on GitHub
<#1109 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABALZX34KOPHPTMBMK22FETWE3WXVANCNFSM6AAAAAARHTSKR4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I have been using an even more conservative (I think) procedure. I alter
local master only from github master. Then merge or rebase into my local
branch rodney-new, push that up to github rodney-new, and let the CI tests
run on it. If they are good enough, then I push local rodney-new to
github master. But now I can't even do step one.
…On 10/24/22 16:05, peter mckinna wrote:
Eric may have better solutions but I do the following.
If I have been making minor changes on master make sure you are on the
master branch
on your local machine.
git checkout master
git branch (to make sure)
git fetch
git pull --rebase origin master (rebase creates commits on your local
master so your changes are the latest - may provoke conflicts)
git push origin master (sends your local master to remote)
If I have created a local branch I merge on my local machine first then do
the push.
git checkout master (make sure you are on master locally)
git fetch
git pull --rebase origin master
git merge other-branch (may have conflicts gti tells you what to do)
git commit -a ( creates a merge commit)
git push origin master (or just git push works for me)
now master branch should be the same on local and remote.
git log (verify your commits are in place)
On Tue, 25 Oct 2022 at 07:30, Rodney M. Bates ***@***.***>
wrote:
> PS:
>
> 1. I am quite sure this is the way I did this last time, some months ago.
>
> 2. I have definitely made no changes to my local master copy since then.
>
> 3. I pushed my rodney-new branch up to github, in case somebody has an
> urgent need for its contents.
>
> 4. I added a bunch of cases to e019. All give compile errors, as expected
> using my latest compiler, built from rodney-new, but don't crash. A
> couple give a second, probably extraneous, compile message.
>
> On 10/24/22 15:01, Rodney Bates wrote:
> > OK, excuse my frustration, but once again, I can't seem to
> > get the most basic things done in git, despite a 300+ page
> > book, a 400+ page book, and lots of helpful emails from last fall.
> >
> > All I am trying at this point is to get my local master branch
> > up to date with the github master branch. I have:
> >
> > ~/proj/m3/git-merge/cm3/master$ git remote -v
> > eric https://github.com/coder5506/cm3.git (fetch)
> > eric https://github.com/coder5506/cm3.git (push)
> > origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
> > origin /home/rodney/proj/m3/git-devel/cm3 (push)
> > upstream https://github.com/modula3/cm3.git (fetch)
> > upstream https://github.com/modula3/cm3.git (push)
> >
> > and have done git fetch:
> >
> > ~/proj/m3/git-merge/cm3/master$ git remote -v
> > eric https://github.com/coder5506/cm3.git (fetch)
> > eric https://github.com/coder5506/cm3.git (push)
> > origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
> > origin /home/rodney/proj/m3/git-devel/cm3 (push)
> > upstream https://github.com/modula3/cm3.git (fetch)
> > upstream https://github.com/modula3/cm3.git (push)
> > ***@***.***:~/proj/m3/git-merge/cm3/master$ git fetch upstream
> > remote: Enumerating objects: 615, done.
> > remote: Counting objects: 100% (614/614), done.
> > remote: Compressing objects: 100% (231/231), done.
> > remote: Total 615 (delta 373), reused 592 (delta 367), pack-reused 1
> > Receiving objects: 100% (615/615), 556.76 KiB | 1.66 MiB/s, done.
> > Resolving deltas: 100% (373/373), completed with 27 local objects.
> > From https://github.com/modula3/cm3
> > 57ee5fe..65ca3e1 master -> upstream/master
> > * [new branch] zcxh -> upstream/zcxh
> >
> > apparently successfully. so all the files of master on github
> > should be copied locally inside my .git, and my "remote"
> > (confusingly misnamed) named upstream should point to my
> > local copy of the latest github.master.head.
> >
> > But:
> >
> > ~/proj/m3/git-merge/cm3/master$ git merge upstream/master
> > fatal: Not possible to fast-forward, aborting.
> > ***@***.***:~/proj/m3/git-merge/cm3/master$ git merge upstream master
> > merge: upstream - not something we can merge
> >
> >
> > Previously, I remember discovering that some git
> > commands call for "upstream/master" and others "upstream master" to
> > name a (local copy of) a branch at a remote location, but I don't find
> > any reference material telling me which, particularly for git merge,
> > so I tried both. Looks like the slash was the right one, but why
> > does it refuse and what to do?
> >
> >
> > On 10/18/22 21:17, peter mckinna wrote:
> >> No worries,
> >>
> >> I have had merge problems of my own in the past.
> >> While you are at it, have a look at e020. It compiles but crashes.
> >> The stderr.pgm file suggests it should produce a runtime
> >> error - invalid cycle in super types.
> >>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <#1109 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABALZX34KOPHPTMBMK22FETWE3WXVANCNFSM6AAAAAARHTSKR4>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub <#1109 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSVZNDIIQRY5SENVUIWEODWE32ZFANCNFSM6AAAAAARHTSKR4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Your local rodney-new should be in sync with the remote, so just
merge into master locally, then push. Are the CI testers making
changes to rodney-new? I'm not sure about remote merging.
This whole CI thing might need examination. I get they are testing
on all architectures but as far as I can tell they are only using the C
backend whereas they should be testing other backends as well.
Also which branches do they test? Surely not all branches. How
would one get them to test a particular branch? And while we are at it,
I think a bit of judicious pruning of some of those github branches would be
benefi
8000
cial.
On Tue, 25 Oct 2022 at 08:53, Rodney M. Bates ***@***.***>
wrote:
… I have been using an even more conservative (I think) procedure. I alter
local master only from github master. Then merge or rebase into my local
branch rodney-new, push that up to github rodney-new, and let the CI tests
run on it. If they are good enough, then I push local rodney-new to
github master. But now I can't even do step one.
On 10/24/22 16:05, peter mckinna wrote:
> Eric may have better solutions but I do the following.
>
> If I have been making minor changes on master make sure you are on the
> master branch
> on your local machine.
>
> git checkout master
> git branch (to make sure)
> git fetch
> git pull --rebase origin master (rebase creates commits on your local
> master so your changes are the latest - may provoke conflicts)
> git push origin master (sends your local master to remote)
>
> If I have created a local branch I merge on my local machine first then
do
> the push.
>
> git checkout master (make sure you are on master locally)
> git fetch
> git pull --rebase origin master
> git merge other-branch (may have conflicts gti tells you what to do)
> git commit -a ( creates a merge commit)
> git push origin master (or just git push works for me)
>
> now master branch should be the same on local and remote.
>
> git log (verify your commits are in place)
>
>
>
>
> On Tue, 25 Oct 2022 at 07:30, Rodney M. Bates ***@***.***>
> wrote:
>
> > PS:
> >
> > 1. I am quite sure this is the way I did this last time, some months
ago.
> >
> > 2. I have definitely made no changes to my local master copy since
then.
> >
> > 3. I pushed my rodney-new branch up to github, in case somebody has an
> > urgent need for its contents.
> >
> > 4. I added a bunch of cases to e019. All give compile errors, as
expected
> > using my latest compiler, built from rodney-new, but don't crash. A
> > couple give a second, probably extraneous, compile message.
> >
> > On 10/24/22 15:01, Rodney Bates wrote:
> > > OK, excuse my frustration, but once again, I can't seem to
> > > get the most basic things done in git, despite a 300+ page
> > > book, a 400+ page book, and lots of helpful emails from last fall.
> > >
> > > All I am trying at this point is to get my local master branch
> > > up to date with the github master branch. I have:
> > >
> > > ~/proj/m3/git-merge/cm3/master$ git remote -v
> > > eric https://github.com/coder5506/cm3.git (fetch)
> > > eric https://github.com/coder5506/cm3.git (push)
> > > origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
> > > origin /home/rodney/proj/m3/git-devel/cm3 (push)
> > > upstream https://github.com/modula3/cm3.git (fetch)
> > > upstream https://github.com/modula3/cm3.git (push)
> > >
> > > and have done git fetch:
> > >
> > > ~/proj/m3/git-merge/cm3/master$ git remote -v
> > > eric https://github.com/coder5506/cm3.git (fetch)
> > > eric https://github.com/coder5506/cm3.git (push)
> > > origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
> > > origin /home/rodney/proj/m3/git-devel/cm3 (push)
> > > upstream https://github.com/modula3/cm3.git (fetch)
> > > upstream https://github.com/modula3/cm3.git (push)
> > > ***@***.***:~/proj/m3/git-merge/cm3/master$ git fetch upstream
> > > remote: Enumerating objects: 615, done.
> > > remote: Counting objects: 100% (614/614), done.
> > > remote: Compressing objects: 100% (231/231), done.
> > > remote: Total 615 (delta 373), reused 592 (delta 367), pack-reused 1
> > > Receiving objects: 100% (615/615), 556.76 KiB | 1.66 MiB/s, done.
> > > Resolving deltas: 100% (373/373), completed with 27 local objects.
> > > From https://github.com/modula3/cm3
> > > 57ee5fe..65ca3e1 master -> upstream/master
> > > * [new branch] zcxh -> upstream/zcxh
> > >
> > > apparently successfully. so all the files of master on github
> > > should be copied locally inside my .git, and my "remote"
> > > (confusingly misnamed) named upstream should point to my
> > > local copy of the latest github.master.head.
> > >
> > > But:
> > >
> > > ~/proj/m3/git-merge/cm3/master$ git merge upstream/master
> > > fatal: Not possible to fast-forward, aborting.
> > > ***@***.***:~/proj/m3/git-merge/cm3/master$ git merge upstream master
> > > merge: upstream - not something we can merge
> > >
> > >
> > > Previously, I remember discovering that some git
> > > commands call for "upstream/master" and others "upstream master" to
> > > name a (local copy of) a branch at a remote location, but I don't
find
> > > any reference material telling me which, particularly for git merge,
> > > so I tried both. Looks like the slash was the right one, but why
> > > does it refuse and what to do?
> > >
> > >
> > > On 10/18/22 21:17, peter mckinna wrote:
> > >> No worries,
> > >>
> > >> I have had merge problems of my own in the past.
> > >> While you are at it, have a look at e020. It compiles but crashes.
> > >> The stderr.pgm file suggests it should produce a runtime
> > >> error - invalid cycle in super types.
> > >>
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <#1109 (comment)>,
or
> > unsubscribe
> > <
https://github.com/notifications/unsubscribe-auth/ABALZX34KOPHPTMBMK22FETWE3WXVANCNFSM6AAAAAARHTSKR4
>
> > .
> > You are receiving this because you authored the thread.Message ID:
> > ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub <
#1109 (comment)>, or
unsubscribe <
https://github.com/notifications/unsubscribe-auth/ABSVZNDIIQRY5SENVUIWEODWE32ZFANCNFSM6AAAAAARHTSKR4
>.
> You are receiving this because you commented.Message ID: ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#1109 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABALZX4HSACTPBLNRB6X2XTWE4AMZANCNFSM6AAAAAARHTSKR4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
As I known, only Rodney making changes in "rodney-new branch" (
Please re-post Your msg to issue N1102 ) |
|
On 10/24/22 17:46, peter mckinna wrote:
Your local rodney-new should be in sync with the remote, so just
merge into master locally, then push. Are the CI testers making
changes to rodney-new?
I don't think so.
I prefer creating a merged (or rebased) local rodney-new and pushing
it first, to avoid risking introducing breakage in github master.
But.. regardless of that, before I can create a merge either way,
I have to get github master to pull down, which is where I am stuck
right now. This used to work.
I'm not sure about remote merging.
This whole CI thing might need examination. I get they are testing
on all architectures but as far as I can tell they are only using the C
backend whereas they should be testing other backends as well.
Also which branches do they test?
\
As of the last time I pushed rodney-new, it provoked tests.
… Surely not all branches. How
would one get them to test a particular branch? And while we are at it,
I think a bit of judicious pruning of some of those github branches would be
beneficial.
On Tue, 25 Oct 2022 at 08:53, Rodney M. Bates ***@***.***>
wrote:
> I have been using an even more conservative (I think) procedure. I alter
> local master only from github master. Then merge or rebase into my local
> branch rodney-new, push that up to github rodney-new, and let the CI tests
> run on it. If they are good enough, then I push local rodney-new to
> github master. But now I can't even do step one.
>
> On 10/24/22 16:05, peter mckinna wrote:
> > Eric may have better solutions but I do the following.
> >
> > If I have been making minor changes on master make sure you are on the
> > master branch
> > on your local machine.
> >
> > git checkout master
> > git branch (to make sure)
> > git fetch
> > git pull --rebase origin master (rebase creates commits on your local
> > master so your changes are the latest - may provoke conflicts)
> > git push origin master (sends your local master to remote)
> >
> > If I have created a local branch I merge on my local machine first then
> do
> > the push.
> >
> > git checkout master (make sure you are on master locally)
> > git fetch
> > git pull --rebase origin master
> > git merge other-branch (may have conflicts gti tells you what to do)
> > git commit -a ( creates a merge commit)
> > git push origin master (or just git push works for me)
> >
> > now master branch should be the same on local and remote.
> >
> > git log (verify your commits are in place)
> >
> >
> >
> >
> > On Tue, 25 Oct 2022 at 07:30, Rodney M. Bates ***@***.***>
> > wrote:
> >
> > > PS:
> > >
> > > 1. I am quite sure this is the way I did this last time, some months
> ago.
> > >
> > > 2. I have definitely made no changes to my local master copy since
> then.
> > >
> > > 3. I pushed my rodney-new branch up to github, in case somebody has an
> > > urgent need for its contents.
> > >
> > > 4. I added a bunch of cases to e019. All give compile errors, as
> expected
> > > using my latest compiler, built from rodney-new, but don't crash. A
> > > couple give a second, probably extraneous, compile message.
> > >
> > > On 10/24/22 15:01, Rodney Bates wrote:
> > > > OK, excuse my frustration, but once again, I can't seem to
> > > > get the most basic things done in git, despite a 300+ page
> > > > book, a 400+ page book, and lots of helpful emails from
8000
last fall.
> > > >
> > > > All I am trying at this point is to get my local master branch
> > > > up to date with the github master branch. I have:
> > > >
> > > > ~/proj/m3/git-merge/cm3/master$ git remote -v
> > > > eric https://github.com/coder5506/cm3.git (fetch)
> > > > eric https://github.com/coder5506/cm3.git (push)
> > > > origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
> > > > origin /home/rodney/proj/m3/git-devel/cm3 (push)
> > > > upstream https://github.com/modula3/cm3.git (fetch)
> > > > upstream https://github.com/modula3/cm3.git (push)
> > > >
> > > > and have done git fetch:
> > > >
> > > > ~/proj/m3/git-merge/cm3/master$ git remote -v
> > > > eric https://github.com/coder5506/cm3.git (fetch)
> > > > eric https://github.com/coder5506/cm3.git (push)
> > > > origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
> > > > origin /home/rodney/proj/m3/git-devel/cm3 (push)
> > > > upstream https://github.com/modula3/cm3.git (fetch)
> > > > upstream https://github.com/modula3/cm3.git (push)
> > > > ***@***.***:~/proj/m3/git-merge/cm3/master$ git fetch upstream
> > > > remote: Enumerating objects: 615, done.
> > > > remote: Counting objects: 100% (614/614), done.
> > > > remote: Compressing objects: 100% (231/231), done.
> > > > remote: Total 615 (delta 373), reused 592 (delta 367), pack-reused 1
> > > > Receiving objects: 100% (615/615), 556.76 KiB | 1.66 MiB/s, done.
> > > > Resolving deltas: 100% (373/373), completed with 27 local objects.
> > > > From https://github.com/modula3/cm3
> > > > 57ee5fe..65ca3e1 master -> upstream/master
> > > > * [new branch] zcxh -> upstream/zcxh
> > > >
> > > > apparently successfully. so all the files of master on github
> > > > should be copied locally inside my .git, and my "remote"
> > > > (confusingly misnamed) named upstream should point to my
> > > > local copy of the latest github.master.head.
> > > >
> > > > But:
> > > >
> > > > ~/proj/m3/git-merge/cm3/master$ git merge upstream/master
> > > > fatal: Not possible to fast-forward, aborting.
> > > > ***@***.***:~/proj/m3/git-merge/cm3/master$ git merge upstream master
> > > > merge: upstream - not something we can merge
> > > >
> > > >
> > > > Previously, I remember discovering that some git
> > > > commands call for "upstream/master" and others "upstream master" to
> > > > name a (local copy of) a branch at a remote location, but I don't
> find
> > > > any reference material telling me which, particularly for git merge,
> > > > so I tried both. Looks like the slash was the right one, but why
> > > > does it refuse and what to do?
> > > >
> > > >
> > > > On 10/18/22 21:17, peter mckinna wrote:
> > > >> No worries,
> > > >>
> > > >> I have had merge problems of my own in the past.
> > > >> While you are at it, have a look at e020. It compiles but crashes.
> > > >> The stderr.pgm file suggests it should produce a runtime
> > > >> error - invalid cycle in super types.
> > > >>
> > > >
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <#1109 (comment)>,
> or
> > > unsubscribe
> > > <
> https://github.com/notifications/unsubscribe-auth/ABALZX34KOPHPTMBMK22FETWE3WXVANCNFSM6AAAAAARHTSKR4
> >
> > > .
> > > You are receiving this because you authored the thread.Message ID:
> > > ***@***.***>
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub <
> #1109 (comment)>, or
> unsubscribe <
> https://github.com/notifications/unsubscribe-auth/ABSVZNDIIQRY5SENVUIWEODWE32ZFANCNFSM6AAAAAARHTSKR4
> >.
> > You are receiving this because you commented.Message ID: ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <#1109 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABALZX4HSACTPBLNRB6X2XTWE4AMZANCNFSM6AAAAAARHTSKR4>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub <#1109 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSVZNFFRN2YUCATIPIH2CDWE4GTZANCNFSM6AAAAAARHTSKR4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
I didn't see a git pull in your earlier email.
You did the fetch which just gets the commits but not
the pull which puts them into the branch. Was that an oversight?
On Thu, 27 Oct 2022 at 03:35, Rodney M. Bates ***@***.***>
wrote:
…
On 10/24/22 17:46, peter mckinna wrote:
> Your local rodney-new should be in sync with the remote, so just
> merge into master locally, then push. Are the CI testers making
> changes to rodney-new?
I don't think so.
I prefer creating a merged (or rebased) local rodney-new and pushing
it first, to avoid risking introducing breakage in github master.
But.. regardless of that, before I can create a merge either way,
I have to get github master to pull down, which is where I am stuck
right now. This used to work.
> I'm not sure about remote merging.
>
> This whole CI thing might need examination. I get they are testing
> on all architectures but as far as I can tell they are only using the C
> backend whereas they should be testing other backends as well.
> Also which branches do they test?
\
As of the last time I pushed rodney-new, it provoked tests.
> Surely not all branches. How
> would one get them to test a particular branch? And while we are at it,
> I think a bit of judicious pruning of some of those github branches
would be
> beneficial.
>
> On Tue, 25 Oct 2022 at 08:53, Rodney M. Bates ***@***.***>
> wrote:
>
> > I have been using an even more conservative (I think) procedure. I
alter
> > local master only from github master. Then merge or rebase into my
local
> > branch rodney-new, push that up to github rodney-new, and let the CI
tests
> > run on it. If they are good enough, then I push local rodney-new to
> > github master. But now I can't even do step one.
> >
> > On 10/24/22 16:05, peter mckinna wrote:
> > > Eric may have better solutions but I do the following.
> > >
> > > If I have been making minor changes on master make sure you are on
the
> > > master branch
> > > on your local machine.
> > >
> > > git checkout master
> > > git branch (to make sure)
> > > git fetch
> > > git pull --rebase origin master (rebase creates commits on your local
> > > master so your changes are the latest - may provoke conflicts)
> > > git push origin master (sends your local master to remote)
> > >
> > > If I have created a local branch I merge on my local machine first
then
> > do
> > > the push.
> > >
> > > git checkout master (make sure you are on master locally)
> > > git fetch
> > > git pull --rebase origin master
> > > git merge other-branch (may have conflicts gti tells you what to do)
> > > git commit -a ( creates a merge commit)
> > > git push origin master (or just git push works for me)
> > >
> > > now master branch should be the same on local and remote.
> > >
> > > git log (verify your commits are in place)
> > >
> > >
> > >
> > >
> > > On Tue, 25 Oct 2022 at 07:30, Rodney M. Bates ***@***.***>
> > > wrote:
> > >
> > > > PS:
> > > >
> > > > 1. I am quite sure this is the way I did this last time, some
months
> > ago.
> > > >
> > > > 2. I have definitely made no changes to my local master copy since
> > then.
> > > >
> > > > 3. I pushed my rodney-new branch up to github, in case somebody
has an
> > > > urgent need for its contents.
> > > >
> > > > 4. I added a bunch of cases to e019. All give compile errors, as
> > expected
> > > > using my latest compiler, built from rodney-new, but don't crash. A
> > > > couple give a second, probably extraneous, compile message.
> > > >
> > > > On 10/24/22 15:01, Rodney Bates wrote:
> > > > > OK, excuse my frustration, but once again, I can't seem to
> > > > > get the most basic things done in git, despite a 300+ page
> > > > > book, a 400+ page book, and lots of helpful emails from last
fall.
> > > > >
> > > > > All I am trying at this point is to get my local master branch
> > > > > up to date with the github master branch. I have:
> > > > >
> > > > > ~/proj/m3/git-merge/cm3/master$ git remote -v
> > > > > eric https://github.com/coder5506/cm3.git (fetch)
> > > > > eric https://github.com/coder5506/cm3.git (push)
> > > > > origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
> > > > > origin /home/rodney/proj/m3/git-devel/cm3 (push)
> > > > > upstream https://github.com/modula3/cm3.git (fetch)
> > > > > upstream https://github.com/modula3/cm3.git (push)
> > > > >
> > > > > and have done git fetch:
> > > > >
> > > > > ~/proj/m3/git-merge/cm3/master$ git remote -v
> > > > > eric https://github.com/coder5506/cm3.git (fetch)
> > > > > eric https://github.com/coder5506/cm3.git (push)
> > > > > origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
> > > > > origin /home/rodney/proj/m3/git-devel/cm3 (push)
> > > > > upstream https://github.com/modula3/cm3.git (fetch)
> > > > > upstream https://github.com/modula3/cm3.git (push)
> > > > > ***@***.***:~/proj/m3/git-merge/cm3/master$ git fetch upstream
> > > > > remote: Enumerating objects: 615, done.
> > > > > remote: Counting objects: 100% (614/614), done.
> > > > > remote: Compressing objects: 100% (231/231), done.
> > > > > remote: Total 615 (delta 373), reused 592 (delta 367),
pack-reused 1
> > > > > Receiving objects: 100% (615/615), 556.76 KiB | 1.66 MiB/s, done.
> > > > > Resolving deltas: 100% (373/373), completed with 27 local
objects.
> > > > > From https://github.com/modula3/cm3
> > > > > 57ee5fe..65ca3e1 master -> upstream/master
> > > > > * [new branch] zcxh -> upstream/zcxh
> > > > >
> > > > > apparently successfully. so all the files of master on github
> > > > > should be copied locally inside my .git, and my "remote"
> > > > > (confusingly misnamed) named upstream should point to my
> > > > > local copy of the latest github.master.head.
> > > > >
> > > > > But:
> > > > >
> > > > > ~/proj/m3/git-merge/cm3/master$ git merge upstream/master
> > > > > fatal: Not possible to fast-forward, aborting.
> > > > > ***@***.***:~/proj/m3/git-merge/cm3/master$ git merge upstream
master
> > > > > merge: upstream - not something we can merge
> > > > >
> > > > >
> > > > > Previously, I remember discovering that some git
> > > > > commands call for "upstream/master" and others "upstream master"
to
> > > > > name a (local copy of) a branch at a remote location, but I don't
> > find
> > > > > any reference material telling me which, particularly for git
merge,
> > > > > so I tried both. Looks like the slash was the right one, but why
> > > > > does it refuse and what to do?
> > > > >
> > > > >
> > > > > On 10/18/22 21:17, peter mckinna wrote:
> > > > >> No worries,
> > > > >>
> > > > >> I have had merge problems of my own in the past.
> > > > >> While you are at it, have a look at e020. It compiles but
crashes.
> > > > >> The stderr.pgm file suggests it should produce a runtime
> > > > >> error - invalid cycle in super types.
> > > > >>
> > > > >
> > > >
> > > > —
> > > > Reply to this email directly, view it on GitHub
> > > > <
#1109 (comment)>,
> > or
> > > > unsubscribe
> > > > <
> >
https://github.com/notifications/unsubscribe-auth/ABALZX34KOPHPTMBMK22FETWE3WXVANCNFSM6AAAAAARHTSKR4
> > >
> > > > .
> > > > You are receiving this because you authored the thread.Message ID:
> > > > ***@***.***>
> > > >
> > >
> > > —
> > > Reply to this email directly, view it on GitHub <
> > #1109 (comment)>,
or
> > unsubscribe <
> >
https://github.com/notifications/unsubscribe-auth/ABSVZNDIIQRY5SENVUIWEODWE32ZFANCNFSM6AAAAAARHTSKR4
> > >.
> > > You are receiving this because you commented.Message ID: ***@***.***>
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <#1109 (comment)>,
or
> > unsubscribe
> > <
https://github.com/notifications/unsubscribe-auth/ABALZX4HSACTPBLNRB6X2XTWE4AMZANCNFSM6AAAAAARHTSKR4
>
> > .
> > You are receiving this because you authored the thread.Message ID:
> > ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub <
#1109 (comment)>, or
unsubscribe <
https://github.com/notifications/unsubscribe-auth/ABSVZNFFRN2YUCATIPIH2CDWE4GTZANCNFSM6AAAAAARHTSKR4
>.
> You are receiving this because you commented.Message ID: ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#1109 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABALZX7ZJUSZN5HCHHXBDGTWFFMTVANCNFSM6AAAAAARHTSKR4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
On 10/26/22 16:46, peter mckinna wrote:
I didn't see a git pull in your earlier email.
You did the fetch which just gets the commits but not
the pull which puts them into the branch. Was that an oversight?
No, no oversight. Per Eric's advice from months ago,
for getting my local master updated, I fetch, then
rebase. But in backscrolling, I see a mistake. I
actually did a merge upstream/master instead of a rebase,
and that was what refused:
:~/proj/m3/git-merge/cm3/master$ git merge upstream/master
fatal: Not possible to fast-forward, aborting.
Moreover, I remember doing some kind of config on merge,
that makes it do fast-forward only, which explains the
refusal to do it another way.
So I tried again with the rebase. That refused too, but
unlike merge, it told me about one simple change to my
local master that explains why fast-forward was impossible.
Fixing that, the rebase worked as expected.
So thanks for the question, as it made me look in the right
place to discover the problem.
…
On Thu, 27 Oct 2022 at 03:35, Rodney M. Bates ***@***.***>
wrote:
>
>
> On 10/24/22 17:46, peter mckinna wrote:
> > Your local rodney-new should be in sync with the remote, so just
> > merge into master locally, then push. Are the CI testers making
> > changes to rodney-new?
>
> I don't think so.
>
> I prefer creating a merged (or rebased) local rodney-new and pushing
> it first, to avoid risking introducing breakage in github master.
> But.. regardless of that, before I can create a merge either way,
> I have to get github master to pull down, which is where I am stuck
> right now. This used to work.
>
> > I'm not sure about remote merging.
> >
> > This whole CI thing might need examination. I get they are testing
> > on all architectures but as far as I can tell they are only using the C
> > backend whereas they should be testing other backends as well.
> > Also which branches do they test?
> \
> As of the last time I pushed rodney-new, it provoked tests.
>
> > Surely not all branches. How
> > would one get them to test a particular branch? And while we are at it,
> > I think a bit of judicious pruning of some of those github branches
> would be
> > beneficial.
> >
> > On Tue, 25 Oct 2022 at 08:53, Rodney M. Bates ***@***.***>
> > wrote:
> >
> > > I have been using an even more conservative (I think) procedure. I
> alter
> > > local master only from github master. Then merge or rebase into my
> local
> > > branch rodney-new, push that up to github rodney-new, and let the CI
> tests
> > > run on it. If they are good enough, then I push local rodney-new to
> > > github master. But now I can't even do step one.
> > >
> > > On 10/24/22 16:05, peter mckinna wrote:
> > > > Eric may have better solutions but I do the following.
> > > >
> > > > If I have been making minor changes on master make sure you are on
> the
> > > > master branch
> > > > on your local machine.
> > > >
> > > > git checkout master
> > > > git branch (to make sure)
> > > > git fetch
> > > > git pull --rebase origin master (rebase creates commits on your local
> > > > master so your changes are the latest - may provoke conflicts)
> > > > git push origin master (sends your local master to remote)
> > > >
> > > > If I have created a local branch I merge on my local machine first
> then
> > > do
> > > > the push.
> > > >
> > > > git checkout master (make sure you are on master locally)
> > > > git fetch
> > > > git pull --rebase origin master
> > > > git merge other-branch (may have conflicts gti tells you what to do)
> > > > git commit -a ( creates a merge commit)
> > > > git push origin master (or just git push works for me)
> > > >
> > > > now master branch should be the same on local and remote.
> > > >
> > > > git log (verify your commits are in place)
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, 25 Oct 2022 at 07:30, Rodney M. Bates ***@***.***>
> > > > wrote:
> > > >
> > > > > PS:
> > > > >
> > > > > 1. I am quite sure this is the way I did this last time, some
> months
> > > ago.
> > > > >
> > > > > 2. I have definitely made no changes to my local master copy since
> > > then.
> > > > >
> > > > > 3. I pushed my rodney-new branch up to github, in case somebody
> has an
> > > > > urgent need for its contents.
> > > > >
> > > > > 4. I added a bunch of cases to e019. All give compile errors, as
> > > expected
> > > > > using my latest compiler, built from rodney-new, but don't crash. A
> > > > > couple give a second, probably extraneous, compile message.
> > > > >
> > > > > On 10/24/22 15:01, Rodney Bates wrote:
> > > > > > OK, excuse my frustration, but once again, I can't seem to
> > > > > > get the most basic things done in git, despite a 300+ page
> > > > > > book, a 400+ page book, and lots of helpful emails from last
> fall.
> > > > > >
> > > > > > All I am trying at this point is to get my local master branch
> > > > > > up to date with the github master branch. I have:
> > > > > >
> > > > > > ~/proj/m3/git-merge/cm3/master$ git remote -v
> > > > > > eric https://github.com/coder5506/cm3.git (fetch)
> > > > > > eric https://github.com/coder5506/cm3.git (push)
> > > > > > origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
> > > > > > origin /home/rodney/proj/m3/git-devel/cm3 (push)
> > > > > > upstream https://github.com/modula3/cm3.git (fetch)
> > > > > > upstream https://github.com/modula3/cm3.git (push)
> > > > > >
> > > > > > and have done git fetch:
> > > > > >
> > > > > > ~/proj/m3/git-merge/cm3/master$ git remote -v
> > > > > > eric https://github.com/coder5506/cm3.git (fetch)
> > > > > > eric https://github.com/coder5506/cm3.git (push)
> > > > > > origin /home/rodney/proj/m3/git-devel/cm3 (fetch)
> > > > > > origin /home/rodney/proj/m3/git-devel/cm3 (push)
> > > > > > upstream https://github.com/modula3/cm3.git (fetch)
> > > > > > upstream https://github.com/modula3/cm3.git (push)
> > > > > > ***@***.***:~/proj/m3/git-merge/cm3/master$ git fetch upstream
> > > > > > remote: Enumerating objects: 615, done.
> > > > > > remote: Counting objects: 100% (614/614), done.
> > > > > > remote: Compressing objects: 100% (231/231), done.
> > > > > > remote: Total 615 (delta 373), reused 592 (delta 367),
> pack-reused 1
> > > > > > Receiving objects: 100% (615/615), 556.76 KiB | 1.66 MiB/s, done.
> > > > > > Resolving deltas: 100% (373/373), completed with 27 local
> objects.
> > > > > > From https://github.com/modula3/cm3
> > > > > > 57ee5fe..65ca3e1 master -> upstream/master
> > > > > > * [new branch] zcxh -> upstream/zcxh
> > > > > >
> > > > > > apparently successfully. so all the files of master on github
> > > > > > should be copied locally inside my .git, and my "remote"
> > > > > > (confusingly misnamed) named upstream should point to my
> > > > > > local copy of the latest github.master.head.
> > > > > >
> > > > > > But:
> > > > > >
> > > > > > ~/proj/m3/git-merge/cm3/master$ git merge upstream/master
> > > > > > fatal: Not possible to fast-forward, aborting.
> > > > > > ***@***.***:~/proj/m3/git-merge/cm3/master$ git merge upstream
> master
> > > > > > merge: upstream - not something we can merge
> > > > > >
> > > > > >
> > > > > > Previously, I remember discovering that some git
> > > > > > commands call for "upstream/master" and others "upstream master"
> to
> > > > > > name a (local copy of) a branch at a remote location, but I don't
> > > find
> > > > > > any reference material telling me which, particularly for git
> merge,
> > > > > > so I tried both. Looks like the slash was the right one, but why
> > > > > > does it refuse and what to do?
> > > > > >
> > > > > >
> > > > > > On 10/18/22 21:17, peter mckinna wrote:
> > > > > >> No worries,
> > > > > >>
> > > > > >> I have had merge problems of my own in the past.
> > > > > >> While you are at it, have a look at e020. It compiles but
> crashes.
> > > > > >> The stderr.pgm file suggests it should produce a runtime
> > > > > >> error - invalid cycle in super types.
> > > > > >>
> > > > > >
> > > > >
> > > > > —
> > > > > Reply to this email directly, view it on GitHub
> > > > > <
> #1109 (comment)>,
> > > or
> > > > > unsubscribe
> > > > > <
> > >
> https://github.com/notifications/unsubscribe-auth/ABALZX34KOPHPTMBMK22FETWE3WXVANCNFSM6AAAAAARHTSKR4
> > > >
> > > > > .
> > > > > You are receiving this because you authored the thread.Message ID:
> > > > > ***@***.***>
> > > > >
> > > >
> > > > —
> > > > Reply to this email directly, view it on GitHub <
> > > #1109 (comment)>,
> or
> > > unsubscribe <
> > >
> https://github.com/notifications/unsubscribe-auth/ABSVZNDIIQRY5SENVUIWEODWE32ZFANCNFSM6AAAAAARHTSKR4
> > > >.
> > > > You are receiving this because you commented.Message ID: ***@***.***>
> > > >
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <#1109 (comment)>,
> or
> > > unsubscribe
> > > <
> https://github.com/notifications/unsubscribe-auth/ABALZX4HSACTPBLNRB6X2XTWE4AMZANCNFSM6AAAAAARHTSKR4
> >
> > > .
> > > You are receiving this because you authored the thread.Message ID:
> > > ***@***.***>
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub <
> #1109 (comment)>, or
> unsubscribe <
> https://github.com/notifications/unsubscribe-auth/ABSVZNFFRN2YUCATIPIH2CDWE4GTZANCNFSM6AAAAAARHTSKR4
> >.
> > You are receiving this because you commented.Message ID: ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <#1109 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABALZX7ZJUSZN5HCHHXBDGTWFFMTVANCNFSM6AAAAAARHTSKR4>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub <#1109 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSVZNHO42WKQZRYYEJ2KRDWFGRDDANCNFSM6AAAAAARHTSKR4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
It looks like, "it's time" to integrate rodney-new branch to master branch Thank! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This code from e019
CONST
N = N + 1l;
causes a segv in the frontend from a stack overflow caused
(ironically) by infinite recursion between Expr.RepTypeOf
and AddExpr.RepTypeOf
similar segv for N - 1, N * 1, N DIV 1 but strangely
not N MOD 1
The text was updated successfully, but these errors were encountered: