phase2: test_bitwise.eigs cites ctl.scan.* rows; the MAP's refusal controls are ctl.N8.refuse-*
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 86/100
Research direction
Read the comment in tests/test_bitwise.eigs and compare its claim with the refusal controls in tests/phase2/MAP.md. Update the comment to name the ctl.N8.refuse-* controls, then run grep -rn 'ctl\.scan' tests tools docs; done means the comment is accurate and the grep finds nothing.
Written by the indexing model from the issue text.
Description
On the phase2-numbers branch (#1758 R1.3, 198c1919), tests/test_bitwise.eigs says the JIT scanner's refusal of the bitwise operators is witnessed by "Phase 2's ctl.scan.* rows":
# R1.3 intentionally scanner-refuses these operators until R5. The hot
# entry/OSR scaffolds below verify interpreted fallback in each setting;
# Phase 2's ctl.scan.* rows independently witness the scanner refusals.
No ctl.scan.* row exists. The controls that witness the refusals are ctl.N8.refuse-band, -bor, -bxor, -shl, -shr, -bnot and -mod in tests/phase2/MAP.md (each with a fn-stop witness that holds at R1.3). The comment is a claim a reader would grep for and not find. It lives only on the integration branch, so it belongs to PR #1776's same-PR docs rule.
Done when
- The comment names the
ctl.N8.refuse-*controls (or the comment is removed when R5 drops the refusal). -
grep -rn 'ctl\.scan' tests tools docsfinds nothing.
- Dominant language
- C
- Stars
- 3
- Forks
- 7
- Avg merge
- 11h 16m
- Merged PRs (30d)
- 267
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from InauguralSystems/EigenScript
-
area:ci area:runtime-vm bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
InauguralSystems/EigenScript#1859 ·
Maintainers usually reply within 1 day
-
area:gates area:gfx found-by:critic kind:gate-defect
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
InauguralSystems/EigenScript#1825 ·
Maintainers usually reply within 1 day
-
Amalgamation compiles with warnings at -O0 (-Wreturn-type) and -O1 (-Wmaybe-uninitialized)Possibly taken @facelessdevhack claimed this 5 days ago. Openarea:embed bug found-by:code-review kind:gate-defect
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
InauguralSystems/EigenScript#1775 ·
Maintainers usually reply within 1 day
-
UB: (int) cast of a user double outside int range in dispatch / vm_index_is_int / flat_index_atOpenarea:runtime-vm kind:silent-wrong
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
InauguralSystems/EigenScript#1748 · 1 comment ·
Maintainers usually reply within 1 day
-
area:gfx bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
InauguralSystems/EigenScript#1684 ·
Maintainers usually reply within 1 day
All issues in InauguralSystems/EigenScript
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
quickjs-ng/quickjs#1836 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
open-quantum-safe/liboqs#2637 ·
Maintainers usually reply within 1 day
-
Go device SDK: Whisper transcriber keeps buffering and transcribing audio appended after Stop()Possibly taken @apoorvdarshan claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#22770 ·
Maintainers usually reply within 1 day
-
fido_do_ecdh() reports any getKeyAgreement failure as FIDO_ERR_INTERNALPossibly taken @brlumen claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
joncampbell123/dosbox-x#6698 ·
Maintainers usually reply within 1 day