[Bug 207599] fixes for kernel built with clang failing to boot on ppc64 qemu

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207599

Mark Millard <markmi at dsl-only.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |markmi at dsl-only.net

--- Comment #1 from Mark Millard <markmi at dsl-only.net> ---
(In reply to Kenneth Salerno from comment #0)

FYI: https://llvm.org/bugs/show_bug.cgi?id=25780 has a list of reports that
FreeBSD requires to be fixed in order for clang to be the system compiler for
powerpc and/or powerpc64. Some of the points are powerpc-only issues but some
of the material also applies to powerpc64. (powerpc64 has had less
checking/testing.)

One of the major things messed up is C++ exception handling, with several
issues contributing to the overall status. That in turn messes up being able to
use kyua for testing: kyua uses C++ exception handling extensively.

The kernel's own code may systematically avoid using some of the messed up code
generation: most of the reported material that was based on testing is for
buildworld attempts for TARGET_ARCH=powerpc. Some of the powerpc64 material was
just noted by someone to be analogous in the clang source code.

Some of the code generation problems are reported to be low probability outside
the C++ exception handling context that forces certain examples of some more
general issues.

If you find more clang powerpc64 code generation problems it would be good to
add more reports on llvm.org/bugs and have them listed in llvm.org/bug's 25780.

It may be that some of the material in the comments for some of the
llvm.org/bugs submittals might eventually need their own submittals if the
fixing-effort is sufficiently distinct. As stands some of the one-line
descriptions only indicate an example of multiple related issues reported in
the comments.

-- 
You are receiving this mail because:
You are the assignee for the bug.