develooper Front page | perl.perl5.porters | Postings from June 2022

Re: Any outstanding branches of op.c? / Split into smaller pieces

Thread Previous | Thread Next
Paul "LeoNerd" Evans
June 6, 2022 11:05
Re: Any outstanding branches of op.c? / Split into smaller pieces
Message ID:
On Sat, 4 Dec 2021 14:16:37 +0000
"Paul \"LeoNerd\" Evans" <> wrote:

> Lately I'm trying to make some edits on op.c, and finding that the
> file has become a giant sprawling monstrosity of way too much code in
> one file; 630k in size and 18k lines of C source code.
> I intend to split it into a few smaller pieces.
> My plan is to create two new .c files to contain subsections of what
> is currently in op.c:
>   peep.c: to contain the finalizer and peephole optimiser
>   ck.c: to contain the opchecker functions (Perl_ck_*)
> This will hopefully end up with a much smaller op.c that contains
> mostly just the lowlevel machinery of being an optree, with the other
> specialised parts of it moved to their own files.

Since we're at the start of the 5.37 development cycle and hopefully
all of the remaining "little edits" that didn't get into 5.36 are done,
I'm going to do this this week.

I have a number of new things I want to introduce into the peephole
optimiser in the coming weeks, so now's probably the best time to make
a start on it.

If anyone does have any outstanding changes to basically any of the
code in op.c, please shout ASAP so we can find a way to not cause too
much merge conflict.

Paul "LeoNerd" Evans      |  |

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About