TONYC Grant Report October 2019

Approximately 32 tickets were reviewed, and 6 patches were
applied

[Hours]         [Activity]
  4.91          #133495 follow-up on Digest::MD5 issues, research (can we
                tell the compiler about unaligned access? Apparently not.
                Check if the compiler optimizes unaligned byte composition
                on x86.  gcc does at -O2 or higher.)
                #133495 polish, testing, apply to blead
                #133495 ticket clean up
  1.68          #134138 testing, apply to blead, perldelta
  3.50          #134349 try to understand code, work on a different
                approach and debugging
                #134349 debug, find what I did wrong, try to reproduce
                other issue, comment with patch
  3.57          #134445 comment
                #134445 review, testing, encounter unrelated MSVC issue
                #134445 discussion with khw, more testing
  0.32          #134466 briefly comment
  0.20          #134467 briefly comment
  0.13          PR #16 - research and briefly comment
  1.50          #17186 rebase no indirect, more tests
                #17186 debugging, testing, push to update PR
  0.10          #17212 research, comment briefly
  0.10          #17220 review, briefly comment
  1.73          #17221 work on fix, creating PR 17239
  2.38          #17223 - reproduce, I think I’ve fixed this before..., fix
                and check for similar issues in the refactor changes
  0.98          PR #17224/ issue #17156 - retest and apply to blead,
                follow-up on sysread/syswrite thread
  0.62          #17226 testing, fix and apply to blead
  0.08          #17229 faster features - rebase and apply to blead
  1.78          #17233 review, research, testing, apply to blead
  0.20          #17238 review
  0.98          #17241 briefly comment
                #17241 test it against issue, review code, briefly comment
  0.97          discussion with khw, research
  3.63          faster feature handling
  0.30          faster feature handling - document ${^FEATURE_BITS}
  0.33          faster feature handling - follow-up
  0.23          faster feature handling - follow-up comment
  0.40          faster feature handling: review, cleanup, make PR
  1.63          more faster feature handling, fixes, polish
  0.95          more research, brief discussion with khw
  0.85          review and apply LeoNerd’s stack documentation patch
  0.37          review build issue, discuss with khw
  0.18          review recent commits for backports
  1.57          utf8-readline: debugging error processing
  0.42          utf8-readline: work on post error processing
  1.32          utf8-readline: work out what’s happening and get tests
                passing, but is it the right test?
======
 37.91 hours total
0
tony
12/2/2019 8:42:14 AM
perl.perl5.porters 47889 articles. 1 followers. Follow

2 Replies
6 Views

Similar Articles

[PageSpeed] 36

+1!


Thanks, Tony!


On 12/2/19 10:42 AM, Tony Cook wrote:
> Approximately 32 tickets were reviewed, and 6 patches were
> applied
>
> [Hours]         [Activity]
>   4.91          #133495 follow-up on Digest::MD5 issues, research (can we
>                 tell the compiler about unaligned access? Apparently not.
>                 Check if the compiler optimizes unaligned byte composition
>                 on x86.  gcc does at -O2 or higher.)
>                 #133495 polish, testing, apply to blead
>                 #133495 ticket clean up
>   1.68          #134138 testing, apply to blead, perldelta
>   3.50          #134349 try to understand code, work on a different
>                 approach and debugging
>                 #134349 debug, find what I did wrong, try to reproduce
>                 other issue, comment with patch
>   3.57          #134445 comment
>                 #134445 review, testing, encounter unrelated MSVC issue
>                 #134445 discussion with khw, more testing
>   0.32          #134466 briefly comment
>   0.20          #134467 briefly comment
>   0.13          PR #16 - research and briefly comment
>   1.50          #17186 rebase no indirect, more tests
>                 #17186 debugging, testing, push to update PR
>   0.10          #17212 research, comment briefly
>   0.10          #17220 review, briefly comment
>   1.73          #17221 work on fix, creating PR 17239
>   2.38          #17223 - reproduce, I think I’ve fixed this before..., fix
>                 and check for similar issues in the refactor changes
>   0.98          PR #17224/ issue #17156 - retest and apply to blead,
>                 follow-up on sysread/syswrite thread
>   0.62          #17226 testing, fix and apply to blead
>   0.08          #17229 faster features - rebase and apply to blead
>   1.78          #17233 review, research, testing, apply to blead
>   0.20          #17238 review
>   0.98          #17241 briefly comment
>                 #17241 test it against issue, review code, briefly comment
>   0.97          discussion with khw, research
>   3.63          faster feature handling
>   0.30          faster feature handling - document ${^FEATURE_BITS}
>   0.33          faster feature handling - follow-up
>   0.23          faster feature handling - follow-up comment
>   0.40          faster feature handling: review, cleanup, make PR
>   1.63          more faster feature handling, fixes, polish
>   0.95          more research, brief discussion with khw
>   0.85          review and apply LeoNerd’s stack documentation patch
>   0.37          review build issue, discuss with khw
>   0.18          review recent commits for backports
>   1.57          utf8-readline: debugging error processing
>   0.42          utf8-readline: work on post error processing
>   1.32          utf8-readline: work out what’s happening and get tests
>                 passing, but is it the right test?
> ======
>  37.91 hours total
>
0
xsawyerx
12/5/2019 8:41:21 PM
--Sig_/TS+BgiroBlkRnx5.XC1sFHb
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks Tony, +1!


On 2019-12-05, at 22:41:21 +0200, Sawyer X wrote:

> +1!
>=20
>=20
> Thanks, Tony!
>=20
>=20
> On 12/2/19 10:42 AM, Tony Cook wrote:
> > Approximately 32 tickets were reviewed, and 6 patches were
> > applied
> >
> > [Hours]         [Activity]
> >   4.91          #133495 follow-up on Digest::MD5 issues, research (can =
we
> >                 tell the compiler about unaligned access? Apparently no=
t.
> >                 Check if the compiler optimizes unaligned byte composit=
ion
> >                 on x86.  gcc does at -O2 or higher.)
> >                 #133495 polish, testing, apply to blead
> >                 #133495 ticket clean up
> >   1.68          #134138 testing, apply to blead, perldelta
> >   3.50          #134349 try to understand code, work on a different
> >                 approach and debugging
> >                 #134349 debug, find what I did wrong, try to reproduce
> >                 other issue, comment with patch
> >   3.57          #134445 comment
> >                 #134445 review, testing, encounter unrelated MSVC issue
> >                 #134445 discussion with khw, more testing
> >   0.32          #134466 briefly comment
> >   0.20          #134467 briefly comment
> >   0.13          PR #16 - research and briefly comment
> >   1.50          #17186 rebase no indirect, more tests
> >                 #17186 debugging, testing, push to update PR
> >   0.10          #17212 research, comment briefly
> >   0.10          #17220 review, briefly comment
> >   1.73          #17221 work on fix, creating PR 17239
> >   2.38          #17223 - reproduce, I think I=E2=80=99ve fixed this bef=
ore..., fix
> >                 and check for similar issues in the refactor changes
> >   0.98          PR #17224/ issue #17156 - retest and apply to blead,
> >                 follow-up on sysread/syswrite thread
> >   0.62          #17226 testing, fix and apply to blead
> >   0.08          #17229 faster features - rebase and apply to blead
> >   1.78          #17233 review, research, testing, apply to blead
> >   0.20          #17238 review
> >   0.98          #17241 briefly comment
> >                 #17241 test it against issue, review code, briefly comm=
ent
> >   0.97          discussion with khw, research
> >   3.63          faster feature handling
> >   0.30          faster feature handling - document ${^FEATURE_BITS}
> >   0.33          faster feature handling - follow-up
> >   0.23          faster feature handling - follow-up comment
> >   0.40          faster feature handling: review, cleanup, make PR
> >   1.63          more faster feature handling, fixes, polish
> >   0.95          more research, brief discussion with khw
> >   0.85          review and apply LeoNerd=E2=80=99s stack documentation =
patch
> >   0.37          review build issue, discuss with khw
> >   0.18          review recent commits for backports
> >   1.57          utf8-readline: debugging error processing
> >   0.42          utf8-readline: work on post error processing
> >   1.32          utf8-readline: work out what=E2=80=99s happening and ge=
t tests
> >                 passing, but is it the right test?
> > =3D=3D=3D=3D=3D=3D
> >  37.91 hours total
> > =20


--=20

--Sig_/TS+BgiroBlkRnx5.XC1sFHb
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQSMNgHejxbagKkr5E35YevWJoC7RgUCXelyfAAKCRD5YevWJoC7
RsOQAJ4p4HkGY8hShQJzp387aFwbDKL+WwCgh0KM1BTDNmZANv4uYHqey9O+ZZU=
=yk2s
-----END PGP SIGNATURE-----

--Sig_/TS+BgiroBlkRnx5.XC1sFHb--
0
mhx
12/5/2019 9:11:24 PM
Reply: