Marius Brehler
Marius Brehler
With the re-worked workflows I close this PR and open a new if required.
Is this issue still up to date? So far it was at least not transferred to [LLVM bug tracker](https://bugs.llvm.org/buglist.cgi?keywords=beginner%2C%20&keywords_type=allwords&list_id=176893&product=MLIR&query_format=advanced&resolution=---), as mentioned in [docs](https://mlir.llvm.org/getting_started/Contributing/).
Thanks for filling the issue @joker-eph. I would be awesome to clarify in which way the logos can be used, amongst other things for my presentation in the LLVM devroom...
Any update on this?
I think something like for the C++ logo would be desirable (https://isocpp.org/home/terms-of-use): > The “Standard C++ Foundation” name and stylized “C++” logo are trademarks of the Standard C++ Foundation and...
Yeah, that was actually the question if the assignment should either move up to where the variables are declared or if the declaration might move down (keeping the position of...
I just wasn't 100% certain, but in the case it is unused, I might send a PR and will refactor the eps_t usage in the specific file a little bit...
We have only limited capacity to test on macOS and our workflow (`CI - macOS arm64 clang`) runs on macOS 14, thus issues with macOS 15 might indeed be uncovered....
I've triggered https://github.com/iree-org/iree/actions/runs/14317900035 that runs on `macos-15`.
> I've triggered https://github.com/iree-org/iree/actions/runs/14317900035 that runs on `macos-15`. The workflow passed in the CI, thus I unfortunately cannot reproduce without further details.