Bug 85948 - MMX/SSE unhandled instruction 'sfence'
Summary: MMX/SSE unhandled instruction 'sfence'
Status: RESOLVED DUPLICATE of bug 85947
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: 2.1.2
Platform: Compiled Sources Linux
: NOR major
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-25 17:12 UTC by Ivan Kalvachev
Modified: 2004-07-25 17:38 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Kalvachev 2004-07-25 17:12:14 UTC 
disInstr: unhandled instruction bytes: 0xF 0xAE 0xF8 0xF
          at 0x80CD05E: fast_memcpy_MMX2 (aclib_template.c:349)

@@ aclib_template.c:346
 #ifdef HAVE_MMX2
                 /* since movntq is weakly-ordered, a "sfence"
                  * is needed to become ordered again. */
                 __asm__ __volatile__ ("sfence":::"memory");
 #endif

I found this when tried to debuging mplayer. My processor don't have SSE support.
This 'sfence' instruction is known as MMX2 (MMXEXT, also know as integer SSE).
It is used together with movntq. I guess that memory written my movntq should
not be read before "sfence" instruction. But for now I only need not to get
error on it.
Comment 1 Ivan Kalvachev 2004-07-25 17:31:31 UTC 
OOps, sorry, my mistake.
I just hit refresh on the page that is active AFTER posting bug.
You can threat it as bugzilla bug ;)
(DUBLICATE)
Comment 2 Tom Hughes 2004-07-25 17:38:46 UTC 
Most browsers warn you if you hit refresh on a page that was posted precisely because reposting the data may be a bad idea.

*** This bug has been marked as a duplicate of 85947 ***