Julian Oppermann

[HW] Pass to flatten !hw.struct types

3

As discussed in the ODM on 5/18/22. The idea is to transform ```mlir hw.module @foo(%in: !hw.struct) -> (out: !hw.struct) { %0 = hw.struct_extract %in["a"] : !hw.struct %1 = hw.struct_extract %in["b"]...

Problem classes in the scheduling infra currently use a macro to define a protected constructor and common members. The original rationale was to be able to use default constructors throughout...

Test whether the copy constructor and assignment operator is usable with `Problem` instances. If not, we should introduce a `clone()` method on the problem hierarchy, to be overridden by subclasses...

`Problem`s contain two kinds of properties, i.e. input and solution properties. A common use-case is to make small modifications to an instance (cf. #7544) and re-schedule. To that end, it...

Currently, `Problem` instances can only be constructed (by adding operations/operator types/dependences), but neither these components nor the properties set for them can be removed again afterwards. We should add methods...

[Scheduling] Logging via the containing op can be too verbose

1

@7FM noted: > I find the logging sometimes a bit too verbose, especially when the `containingOp` is very large. A hacky workaround that I sometimes use OoT is something like...

This PR sets up in-memory compilation for runtime-defined SYCL kernels, via clang's libtooling interface and reusing LLVM-to-SPRIV-translation infrastructure in sycl-jit. I introduced a new, undocumented source language `sycljit`, which shall...