Skip to content

Conversation

@jhuber6
Copy link
Contributor

@jhuber6 jhuber6 commented Apr 21, 2025

Summary:
This patch changes the handling for default in the LLVM runtimes list.
Currently it's some different path, but I think it's more
straightforward if we have everything go through the same handling and
just semantically replace default with the target LLVM is building for
(current behavior).

The one thing that this changes I'm aware of is that instead of
something like ninja check-libc we now have ninja check-libc-x86_64-unknown-linux-gnu. This will almost surely break some
bots with hard-coded check projects, so I'm thinking the easiest
solution is to always define the check-<runtime> and every time we
add a specific target, it adds itself as a dependency to the global
check-<runtime>.

Summary:
This patch changes the handling for `default` in the LLVM runtimes list.
Currently it's some different path, but I think it's more
straightforward if we have everything go through the same handling and
just semantically replace `default` with the target LLVM is building for
(current behavior).

The one thing that this changes I'm aware of is that instead of
something like `ninja check-libc` we now have `ninja
check-libc-x86_64-unknown-linux-gnu`. This will almost surely break some
bots with hard-coded check projects, so I'm thinking the easiest
solution is to *always* define the `check-<runtime>` and every time we
add a specific target, it adds itself as a dependency to the global
`check-<runtime>`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant