[CIR][Lowering] Core dialects: passthrough symbol visibility #1620
Conversation
…to created func.func in cirtomlir lowering
… when convertion MLIR core module to LLVM MLIR module + added removal of unnecessary CIR Attr
felixdaas
force-pushed
the
convertCIRTargetTriple
branch
from
adee41c to
280bb46
Compare
|
Hey, I’ve added two test cases that are very similar to the examples I mentioned in the issue description. As expected, the tests failed without the changes and passed with them. This is my first time writing tests with lit/FileCheck, so if you notice anything that could be improved, I’d appreciate your feedback — but they might already be fine as they are. I was also unsure about the naming, so if you have better suggestions, feel free to let me know. |
…onstraint to compilation test to fix execution on windows and mac
|
Thanks for the feedback! I've implemented the requested changes. Additionally, I added the -triple x86_64-unknown-linux-gnu option to the %clang_cc1 invocation in the declaration.c test, following the pattern used in other ThroughMLIR tests. I also constrained the compilation test to run only on x86_64 Linux targets, so hopefully both will now pass on Windows and macOS as well. I wasn't entirely sure which other targets to include. Based on CIRGenModule::getTargetCIRGenInfo(), it might make sense to relax the constraints in the future to support certain aarch64 targets (and possibly spirv64, nvptx, and amdgcn). But for now, I’ve conservatively limited the test to x86_64 Linux only. |
bcardosolopes
changed the title
|
(and btw @bcardosolopes thanks for all the help and info on this PR and sorry about missing your suggestion about the space identation earlier) |
Fixes #1619
Fixes #1618