[valgrind] [Bug 398883] valgrind incorrectly assumes ABI on PowerPC based on endianness

2019-05-14 Thread Brandon Bergren
https://bugs.kde.org/show_bug.cgi?id=398883

--- Comment #7 from Brandon Bergren  ---
Ahh, I think we were using different meanings for the word "supported". I was
speaking in terms of "what can the hardware do, is specified in the ABI, and is
currently in use in the wild", not "what you can actually get official support
for".

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 398883] valgrind incorrectly assumes ABI on PowerPC based on endianness

2019-03-11 Thread Brandon Bergren
https://bugs.kde.org/show_bug.cgi?id=398883

Brandon Bergren  changed:

   What|Removed |Added

 CC||k...@bdragon.rtk0.net

--- Comment #6 from Brandon Bergren  ---
While I agree that using ELFv1 on LE is a completely unsupported configuration
and need not be supported, the OpenPOWER ELF V2 ABI is fully defined and
intended for use in both little- and big-endian environments.

Due to the improved toolchain support (specifically, lld's dropping of ELFv1
support entirely, and ELFv2 being a lot less "weird" of an ABI meaning it tends
to have less esoteric issues and can more easily leverage mainstream
optimizations) I see the future of BE on POWER to be ELFv2 as well.

And yes, FreeBSD is moving towards ELFv2 at a rapid pace. (I personally am
running ELFv2 userlands exclusively in FreeBSD on my POWER9 machines.)

-- 
You are receiving this mail because:
You are watching all bug changes.