# Applicant Assessment

Welcome to the applicant assessment. On top of your proposals, we also prepared some coding and short answer questions to assess your readiness for this project.

欢迎来到申请书考核阶段。除了申请书本身的质量外，我们还准备了一些代码和问答题，以便考验你们是否为该 OSPP 项目做好了准备。

Note: the quality of the comments are not assessed.

注：代码题不考核注释质量。

You may answer in either Chinese or English. 中英文皆可用于答题。

1. Please implement `MacroAssembler::sub32FromMemAndBranchIfNegativeWithPatch` and `MacroAssembler::patchSub32FromMemAndBranchIfNegative` for riscv64 properly. Send your work as a patch file attachment, e.g. `patch1.patch`.
   请为 riscv64 正确实现 `MacroAssembler::sub32FromMemAndBranchIfNegativeWithPatch` 和 `MacroAssembler::patchSub32FromMemAndBranchIfNegative`，并在邮件中附上对应的补丁文件，如 `patch1.patch`。
2. Are there bugs to be fixed for riscv64 in `js/src/jit/MacroAssembler.cpp`? If there are, please fix one and send your fix as a patch file attachment.
   `js/src/jit/MacroAssembler.cpp` 有 riscv64 平台需要修复的 bug 吗？若有，请修复一个并附上对应的补丁文件。
3. It's more convenient to evaluate our work on the simulator. Does SpiderMonkey's riscv64 simulator have bugs? If there are, Describe one and show us how you plan to fix it, and what files will be changed by this fix.
   用模拟器来检验修复成果会比实机更方便。那么 riscv64 模拟器有 bug 么？如果有，简单介绍一下是什么 bug、你准备怎么修、以及这个修改会动哪些文件。
4. Are there occurrences of MOZ_CRASH test failures that should not be fixed by modifying the riscv64 backend? If there are, explain why.
   有没有不应该通过修 riscv64 后端来解决的 MOZ_CRASH 测试失败场景？如果有，介绍一下为什么不该这么修。