Bug 145480 - [PATCH] POWER5+/POWER6 instructions: frip, frin, friz, frim, cmpb, mftgpr, mffgpr
Summary: [PATCH] POWER5+/POWER6 instructions: frip, frin, friz, frim, cmpb, mftgpr, mf...
Status: REPORTED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-16 02:56 UTC by Pete Eberlein
Modified: 2016-07-18 17:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
POWER5+/POWER6 instructions patch (22.76 KB, patch)
2007-05-16 02:57 UTC, Pete Eberlein 		Details
POWER5+/POWER6 instructions patch for 3.2.3 (4.76 KB, patch)
2007-06-27 23:16 UTC, Pete Eberlein 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Pete Eberlein 2007-05-16 02:56:34 UTC 
Version:            (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

Attached is a patch to add POWER5+ and POWER6 instruction support to Valgrind, with 4 regression tests.  The following instructions were added:

POWER5+: frip, frim, friz, frin
POWER6: cmpb, mftgpr, mffgpr

The cmpb instruction requires Altivec, since it uses vector operations.
Comment 1 Pete Eberlein 2007-05-16 02:57:18 UTC 
Created attachment 20579 [details]
POWER5+/POWER6 instructions patch
Comment 2 Pete Eberlein 2007-06-27 23:16:47 UTC 
Created attachment 20984 [details]
POWER5+/POWER6 instructions patch for 3.2.3

Added an optional patch that can be applied to Valgrind 3.2.3 release
Comment 3 Andrew Pinski 2008-08-03 18:47:47 UTC 
Hmm, I noticed one thing which I think is wrong.  There should be no difference between 32bit mode and 64bit mode for those instructions really.  They are never implemented on a 32bit processor, only a 64bit one.

-- Pinski
Comment 4 Will Schmidt 2016-07-18 17:11:01 UTC 
Looks like the associated patches for this bug went into valgrind as 
"r11338 | sewardj | 2010-09-03 18:49:33 -0500 (Fri, 03 Sep 2010) | 4 lines"..   should be able to mark this one out as "resolved".