You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we don't have code generation for these, I would rather not accept them in Clang/LLVM. Are these configurations actually used by anyone or are these just remnants of something that hasn't been used in years? If the latter, can they just be removed?
Are these configurations actually used by anyone or are these just remnants of something that hasn't been used in years?
The configurations are still in the tree, so people build them. Whether or not the resulting kernels are actually being booted and used in the wild, let alone with clang, is a completely different story and it is probably hard to figure out, since many hobbyists are not vocal about their usage as long as things stay working. The 32-bit processors are a dying breed obviously (although seemingly still sold in certain applications), so it is probably a waste of resources to try and implement code generation support for them.
For the record, this is being workaround in the kernel by preventing those configurations from being selected:
See also 4b10306.
So
cell
,e6500
,405
,464
,476
,860
,e300c2
, ande300c3
support is missing from clang.These configs set the
-mcpu
value inlinux/arch/powerpc/platforms/Kconfig.cputype
Lines 193 to 205 in 83d09ad
cc @nemanjai
The text was updated successfully, but these errors were encountered: