TestFrameFormatNameWithArgs.test is enabled only in case of native
compilation but is applicable in case of cross compilation too. So,
provision support for enabling it in case of both, native and cross
compilation.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
lldb/test/Shell/helper/build.py | ||
---|---|---|
29 | Why was this needed? Other than that, LGTM |
lldb/test/Shell/helper/build.py | ||
---|---|---|
29 | IIUC, ~/lldb/test/Shell/helper/toolchain.py supplies LLDB's bitness (and not the target architecture) as arch to ~/lldb/test/Shell/helper/build.py unconditionally. However, we may require the target architecture too to customize the compile and link commands (we did in our downstream project, at least). Perhaps, we'd like both, LLDB's bitness and the target architecture to be supplied via separate options but I thought that lifting the restriction in question might've sufficed until we'd provisioned support for the same. Let me know if we'd like it handled (or, not dealt with at all) in this change itself, though, please. |
lldb/test/Shell/helper/build.py | ||
---|---|---|
29 | Ah I see. So you're saying currently the build scripts conflate -m32/-m64 with the -march=<...> flags? Seems like a separate option for bitness vs. arch would be the way to go This current patch could be split into a stack of 3:
and an independent patch
|
Why was this needed?
Other than that, LGTM