🟡 Medium Priority

在掩码寄存器连续非对齐搬出的调用示例（新增）中，第154行使用了 asc_update_src_b16(remain_count) 来准备源操作数。但在整个代码库（include/ 和 impl/ 目录）中均未找到 asc_update_src_b16 的定义。用户若照搬此示例代码将遇到编译错误（未定义标识符），导致文档的指导价值受损。

触发条件：用户复制粘贴该示例代码进行编译时。

建议：将 asc_update_src_b16 替换为实际存在的函数名，或补充该函数的声明和文档，或在注释中标注该行为示意代码（需用户自行实现）。

🟡 Medium Priority

The test test_enable_hf32.cpp (npu_arch_3510) verifies asc_enable_hf32() by only mocking get_ctrl and set_ctrl. It does NOT mock sbitset1 and does NOT verify which value is written to the control register. Compare with the analogous test_enable_hif8.cpp which mocks sbitset1 with precise bit-position verification, and test_set_fp32_mode.cpp which mocks sbitset0 similarly.

The implementation asc_enable_hf32_impl() sets bit 46 via sbitset1(get_ctrl(), HF32_MODE_BIT). Without mocking sbitset1, the test cannot verify:

• that set_ctrl receives the expected result

If sbitset1 is called as a real function during the test (rather than being intercepted by mockcpp), the test might pass even if the bit position is wrong, since set_ctrl is mocked to accept any value via MOCKER_CPP(set_ctrl, void(uint64_t)).times(1).

Changed lines: 28-35 — the test body lacks MOCKER_CPP(sbitset1, ...) and the stubs for sbitset1 / set_ctrl value verification.

建议：Add sbitset1 mock with bit-position verification, and add a set_ctrl stub that verifies the expected value, consistent with test_enable_hif8.cpp:

🟡 Medium Priority

The old test code (test_asc_create_iter_reg.cpp, lines 43-69 in the old version) included TEST_VECTOR_COMPUTE_CREATE_ITER_REG_CUBE tests that set g_coreType = C_API_AIC_TYPE in SetUp and verified that vag_b32/vag_b16/vag_b8 were called zero times (.times(0)). This validated that when ASC_IS_AIC is true, the implementation correctly returns iter_reg{} without calling the hardware intrinsic.

The new code replaces this with TEST_CREATE_ITER_REG_AIV which does NOT set g_coreType (defaulting to AIV) and only tests the AIV path. The AIC path where vag_bxx must NOT be called is now untested. If the if ASC_IS_AIV guard is accidentally removed, the AIC path would incorrectly call vag_bxx and no test would catch it.

Changed lines: entire file rewrite, the old TEST_VECTOR_COMPUTE_CREATE_ITER_REG_CUBE macro and its three instantiations (lines 43-69 old) were removed without replacement.

建议：Add back AIC mode tests. Either: (1) add a macro similar to the old TEST_VECTOR_COMPUTE_CREATE_ITER_REG_CUBE that sets g_coreType = C_API_AIC_TYPE and mocks vag_bxx with .times(0), or (2) add a second macro parameter to the existing TEST_CREATE_ITER_REG_AIV to optionally set coreType and expected call count, so both paths are covered.