Bruno Cardoso Lopes

I understand your question, but I don't understand the specifics: > I find that some libc functions lowering to mlir can use func.call methods, however, I think it is not...

> for library function calls like libc, we haven't found a good solution to lower them to MLIR yet Can you elaborate on why func.call isn't good enough? Are you...

Yep, and there's enough work for multiple folks!

See commented tests in `clang/test/CIR/CodeGen/aarch64-neon-intrinsics.c`. This is just a subset, there is even more if you search in `clang/test/CodeGen`.

@khoipkv Here's a list of ones I'd give priority: ``` Start with: NEON::BI__builtin_neon_vld1_lane_v NEON::BI__builtin_neon_vld1q_lane_v NEON::BI__builtin_neon_vst1_lane_v NEON::BI__builtin_neon_vst1q_lane_v NEON::BI__builtin_neon_vld1_dup_v NEON::BI__builtin_neon_vld1q_dup_v Next ones: NEON::BI__builtin_neon_vsetq_lane_f64 NEON::BI__builtin_neon_vdups_lane_i32 NEON::BI__builtin_neon_vrshrn_n_v NEON::BI__builtin_neon_vget_lane_i8 NEON::BI__builtin_neon_vdupb_lane_i8 clang::AArch64::BI__builtin_arm_ldrex clang::AArch64::BI__builtin_arm_ldaex NEON::BI__builtin_neon_vqrshrun_n_v NEON::BI__builtin_neon_vsra_n_v NEON::BI__builtin_neon_vsraq_n_v...

Hi, welcome. These indeed are good ones. Assigned!

Since you are already working on this and they are all related, this PR should also fix the other issues and include testscases from #521 and #522

> It becomes a little complex when we consider `case` across scope Oh right, you don't need to solve this problem for the moment, let's focus on the testcases that...

Let me know when this comes out of Draft state and I'll take a look again

Let me know once this is ready for review again!