ppc@ On Wed, Feb 05, 2020 at 05:52:47AM +0900, rgc wrote: > On Tue, Feb 04, 2020 at 10:23:09PM +0900, rgc wrote: > > ppc@ > > > > here's a quick n dirty update about macppc and clang > > : > > : > > when a full backup finishes. i'll run a GENERIC kernel on my G4. > > a) clang-compiled kernel and gcc-compiled (stock) ofwboot NG > stops after initializing Jasper > > b) clang-compiled kernel and clang-compiled ofwboot NG > stops after initializing Jasper > > i can get on UKC on both > > it is something to check this weekend
i dived head first, eyes closed to a deep pit ... it seems things i've noticed ... these are mainly diferences in the generated code by gcc and clang. 1 clang is generating .data.rel.ro sections even when -fno-pie is used in the compile option but ... ld handles it. 2 clang generates code R_PPC_PLTREL code, from the lists it is an optimazation that should be handled by the linker ... again ld handles it. 3 clang defaults to -fstack-protector-strong according to clang-local(1) and was verified in the actual llvm code. current gcc just uses -fstack-protector, the lowest level by default. the RAMDISK has -fno-stack-protector ... if i compile GENERIC with NO_PROPOLICE (which also forces the use of -fno-stack-protector) the kernel boots until it hits a Data Access exception ... which might have been caused by either #1 or #2 above. i have VERY ugly mdifications for llvm for #1 and #2 but even with those, the boot does not progress much (well i get several periphs detected on qemu). yorosiku ~
