JiT include update

[jeremylt]

Update JiT to -I all the JiT directories set on the Ceed.

Note: Most of the changes are repeated ripple effects from the core changes it ceed-[cuda,hip]-compile.h.

1. Allow searching of dirs set with CeedAddJitSourceRoot for #include <foo.h>

2. Add CEED_RUNNING_JIT_PASS to guard files that cannot be included for JiT (math.h or std*.h)

3. Prefer ceed/types.h over ceed.h in QF source

4. Redirect ceed.h to ceed/types.h over ceed/ceed.h when CEED_RUNNING_JIT_PASS is set

5. Use include statements instead of loading string buffers for JiT

Ok, here's a rough prototype of an idea @jedbrown. This allows #include <foo.h> (stripping out #include <std*.h>) and would add all JiT dirs as -I/include/this/dir flags to the CUDA/HIP JiT compilers.

Very rough and not rigorously tested but seems to work locally with hacky manual testing.

[jedbrown]

Probably this means we could delete code related to actually finding those headers and reading them. At a glance, this looks good and presumably reduces the volume of output when using CEED_DEBUG=1.

[jrwrigh]

Probably this means we could delete code related to actually finding those headers and reading them.

I'm guessing the OpenCL online compiler has similar functionality, but we'll need to check that for the SYCL backends.

[jeremylt]

Need to run full suite tomorrow, but seems fine with Ratel (should be)

[jeremylt]

Ratel is happy. Noether looks happy.

I say we merge this and do further improvements as follow-up.

[NamjaeChoi]

Hello, I checked out your branch and tested it, but the error persists:
/data/choin/moose/libCEED/interface/ceed-jit-tools.c:138 in CeedLoadSourceToInitializedBuffer(): Couldn't open source file: /data/choin/projects/moose/framework/build/header_symlinks/Kokkos_Core.hpp
This file is in another directory and I provided that directory to CeedAddJitSourceRoot. ~/header_symlinks is where the QFunction source is located.

[jeremylt]

This remains really difficult for me to fully understand without the actual code generating the issue

[jeremylt]

Guessing here, if you are using a local include #include "Kokkos_Core.hpp" instead of #include <Kokkos_Core.hpp>, then as we talked about in the other thread, that local include is still being interpreted as a relative path from the QFunction source file during code generation.

[NamjaeChoi]

Ah so #include "header.h" still searches for the local directory only?

[jeremylt]

Yes, at this time we're still interpreting #include "foo.h" as a local file

[NamjaeChoi]

Changing to #include <header.h> seems to work. Let me try further. Thank you!

[NamjaeChoi]

Do you plan to change the behavior of #include "header.h" as well?

[jeremylt]

Not in this PR, no.

See: #1695 (reply in thread)