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

2023-04-25 Thread A. Wilcox
https://bugs.kde.org/show_bug.cgi?id=398883 --- Comment #10 from A. Wilcox (awilfox) --- Indeed, the only technical issue with this patch is that it is outdated. We have an updated version. I will upload the new version to this bug some time this week after testing it against the latest

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

2023-04-25 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=398883 --- Comment #9 from Carl Love --- I looked thru the patch. Nothing jumps out at me as being an issue. But, that doesn't guarantee anything given the assembly and all. I did try to apply the patch to test it but it doesn't apply. So, I would say,

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

2023-04-24 Thread Sam James
https://bugs.kde.org/show_bug.cgi?id=398883 --- Comment #8 from Sam James --- (In reply to Carl Love from comment #4) > > Given that IBM does not recommend using ELFv1 on Little endian and ELFv2 on > Big endian, that is not to say it can't be done. The proposed patch is not > necessarily

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

2023-01-22 Thread Sam James
https://bugs.kde.org/show_bug.cgi?id=398883 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail

[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

[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

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

2019-03-11 Thread A. Wilcox
https://bugs.kde.org/show_bug.cgi?id=398883 --- Comment #5 from A. Wilcox (awilfox) --- I noted that it was specifically older versions of OpenSuSE. Specifically, the very first release. I believe it is long deprecated; it still, however, does exist. > Similarly, with the musl libc. From my

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

2019-03-11 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=398883 --- Comment #4 from Carl Love --- IBM only supports ELFv1 ABI on Big endian machines and ELFv2 ABI on Little endian machines. I checked a little on the statements about the ELF usages. >From what I was told OpenSuSE uses ELFv2 ABI on little endian.

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

2019-03-09 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=398883 Julian Seward changed: What|Removed |Added CC||c...@us.ibm.com --- Comment #3 from Julian

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

2018-09-27 Thread awilfox
https://bugs.kde.org/show_bug.cgi?id=398883 A. Wilcox (awilfox) changed: What|Removed |Added Attachment #115278|application/mbox|text/plain mime type|

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

2018-09-27 Thread awilfox
https://bugs.kde.org/show_bug.cgi?id=398883 --- Comment #2 from A. Wilcox (awilfox) --- Created attachment 115278 --> https://bugs.kde.org/attachment.cgi?id=115278=edit Ensure ELFv2 is supported on PPC64 This patch has been tested on PPC64 BE, both ELFv1 (Debian) and ELFv2 (Adélie). I don't

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

2018-09-25 Thread awilfox
https://bugs.kde.org/show_bug.cgi?id=398883 --- Comment #1 from A. Wilcox (awilfox) --- Okay, it doesn't have to be so hard. There is already VG_PLAT_USES_PPCTOC; so this change just needs to actually use that define instead of just endianness to determine what ABI to use. -- You are