I got a notice this morning of the latest fix for
covering the TARGET_ARCH=powerpc stack-handling issues
for llvm bugzilla 26519:
> Comment # 33 on bug 26519 from Krzysztof Parzyszek
> The fix has been committed in master in r303257.
>
> I opened PR33070 to request merging it into 4.0.1.
>
> You are receiving this mail because:
> • You reported the bug.
I've been using a version of the patch for some time
and for buildworld it appears that with it powerpc
and powerpc64 have a similar status: the one known
area not working is handling of thrown C++ exceptions
--for example the required dwarf information is
incomplete so programs crash.
(I have one powerpc64 patch in use that is not
applied upstream or in FreeBSD that is essential
for the powerpc64 status. See the later side
notes for the tiny patch.)
For buildkernel there is a difference for
TARGET_ARCH=powerpc vs. TARGET_ARCH=powerpc64 :
A) powerpc46 works for building and running the
kernel and world on the old G5 PowerMacs.
B) powerpc FreeBSD on the same machines fails at
the /sbin/init attempt and then gets an
alignment exception. (I've not tried a G4
or G3 yet.)
As of yet I've no clue why (B) is an issue.
Side notes:
Note 0:
The patch I was given a fair time ago that
is required for TARGET_ARCH=powerpc64 is:
# svnlite diff /usr/src/contrib/llvm/tools/
Index: /usr/src/contrib/llvm/tools/lld/ELF/Target.cpp
===================================================================
--- /usr/src/contrib/llvm/tools/lld/ELF/Target.cpp (revision 317820)
+++ /usr/src/contrib/llvm/tools/lld/ELF/Target.cpp (working copy)
@@ -1070,7 +1070,8 @@
}
PPC64TargetInfo::PPC64TargetInfo() {
- PltRel = GotRel = R_PPC64_GLOB_DAT;
+ GotRel = R_PPC64_GLOB_DAT;
+ PltRel = R_PPC64_JMP_SLOT;
RelativeRel = R_PPC64_RELATIVE;
GotEntrySize = 8;
(Thanks to Roman Divacky.)
Note 1:
While a pure gcc 4.2.1 buildworld buildkernel with
a debug kernel is working for booting and using,
a production style kernel gets occasional panics
on the old G5 PowerMacs. (The powerpc64 builds
work fine on the same machines.) (I've not tried
any G4's or a G3 yet.)
It also appears that small changes in memory
layout details (from trying to get better
evidence) change the behavior/failure-mode/
details. I do not expect to find out what is
going on any time soon.
The same problems existed when buildworld was
via clang 4. A kernel from a clang buildkernel
does not get far enough for me to see what it
would do for the issue.
As this issue is more fundamental to general
operation it has been getting much of my
FreeBSD time.
===
Mark Millard
markmi at dsl-only.net
_______________________________________________
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
