On Mon, 5 Feb 2024 10:37:59 GMT, Magnus Ihse Bursie wrote:
> I'll have a look. It is definitely cleaner if it works.
Yeah, no, as expected it did not work.
-
PR Comment: https://git.openjdk.org/jdk/pull/17688#issuecomment-1926726543
On Fri, 2 Feb 2024 15:27:39 GMT, Magnus Ihse Bursie wrote:
> While we do not have automatic testing of using clang instead of gcc on
> linux, we try to keep it in working condition. This is still the case for the
> JDK itself, but there is a native test which fails to compile with clang.
>
On Mon, 5 Feb 2024 10:12:30 GMT, Magnus Ihse Bursie wrote:
> Any takers on this?
Have an obligatory +1 for the build changes I suppose, but isn't there the
ability to use DISABLED_WARNINGS or a #pragma clang for this?
-
PR Comment:
On Fri, 2 Feb 2024 15:27:39 GMT, Magnus Ihse Bursie wrote:
> While we do not have automatic testing of using clang instead of gcc on
> linux, we try to keep it in working condition. This is still the case for the
> JDK itself, but there is a native test which fails to compile with clang.
>
On Fri, 2 Feb 2024 15:27:39 GMT, Magnus Ihse Bursie wrote:
> While we do not have automatic testing of using clang instead of gcc on
> linux, we try to keep it in working condition. This is still the case for the
> JDK itself, but there is a native test which fails to compile with clang.
>
On Fri, 2 Feb 2024 15:27:39 GMT, Magnus Ihse Bursie wrote:
> While we do not have automatic testing of using clang instead of gcc on
> linux, we try to keep it in working condition. This is still the case for the
> JDK itself, but there is a native test which fails to compile with clang.
>
While we do not have automatic testing of using clang instead of gcc on linux,
we try to keep it in working condition. This is still the case for the JDK
itself, but there is a native test which fails to compile with clang. This
should be fixed.
-
Commit messages:
- 8325176:
