[SYCL] Disable inlining kernel lambda operator at -O0

[premanandrao]

PR #6977 enabled always inlining kernel lambda operators.
This PR disables this at -O0 as it was leading to a poor
debugging experience.

[premanandrao]

The three failing tests in the CUDA LLVM test suite:
Failed Tests (3):
SYCL :: BFloat16/bfloat16_builtins.cpp
SYCL :: Matrix/element_wise_wi_marray_legacy.cpp
SYCL :: Matrix/joint_matrix_tensorcores_legacy.cpp
seem to be bloat16 related.

[pvchupin]

#7567 should fix fails.

[premanandrao]

@pvchupin, the CUDA LLVM test suite is failing for reasons not clear to me.

[premanandrao]

Temporarily moving this to draft state since it looks like passing the flag to additional components may be necessary.

[premanandrao]

Sorry, that was a false alarm due to incorrect environment setup. This is ready for review.

[mdtoguchi]

LGTM, thanks!

[premanandrao]

@pvchupin, the tests seem to be failing again, though there were no compiler changes between yesterday (when it all succeeded) and now. (I did change a test based on code-review, and that test does pass.)

Could you please review the doc change and if you are okay with that, merge the change?

[pvchupin]

As far as I remember clang has -O0 by default?

Suggested change

	Enabled by default; disabled when optimizations are disabled (-O0 or
	equivalent).
	Disabled when optimizations are disabled (-O0 or
	equivalent). Enabled otherwise.

[premanandrao]

Done, thanks.

[pvchupin]

@premanandrao, error when toolchain archive is not found happens usually when you restart failed task manually. When you update the patch you don't need to do anything actually, testing will restart automatically. In the cases when you really want to restart testing the only option is to "Restart all tasks". The reason is that toolchain artifact is erased on the runner as soon as testing is over. Restarting just llvm-test-suite testing is not possible today.

[premanandrao]

@premanandrao, error when toolchain archive is not found happens usually when you restart failed task manually. When you update the patch you don't need to do anything actually, testing will restart automatically. In the cases when you really want to restart testing the only option is to "Restart all tasks". The reason is that toolchain artifact is erased on the runner as soon as testing is over. Restarting just llvm-test-suite testing is not possible today.

Thanks, that is helpful. In my case, testing had started automatically after patch update, and that testing failed cryptically - like with a failed cloud service message. I realize now that I should not have attempted to restart as it seems the original failure info is lost.

[premanandrao]

Failing tests are unrelated to this change.

@pvchupin / @intel/llvm-gatekeepers, this is ready for a merge.