Bug 16385 - Illegal instruction "pfmul" in Mesa with Intel CPU
Summary: Illegal instruction "pfmul" in Mesa with Intel CPU
Status: RESOLVED DUPLICATE of bug 8724
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-16 20:20 UTC by WuNian
Modified: 2009-08-24 12:30 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description WuNian 2008-06-16 20:20:09 UTC 
The "pfmul" is a 3DNow! instruction, Intel chip does not support it.

When I run 3D app, it reported "Illegal instruction" for pfmul:

Program received signal SIGILL, Illegal instruction.
[Switching to Thread 139665477953280 (LWP 6149)]
p4_3d_no_rot_loop () at x86-64/xform4.S:245
245             pfmul %mm0, %mm4                /* x1*m11          | x0*m00          */
Current language:  auto; currently asm
(gdb) bt
#0  p4_3d_no_rot_loop () at x86-64/xform4.S:245
#1  0x00007f0666d940f9 in run_vertex_stage (ctx=0xb1e7d0,
    stage=<value optimized out>) at tnl/t_vb_vertex.c:144
#2  0x00007f0666d8a6bb in _tnl_run_pipeline (ctx=0xb1e7d0)
    at tnl/t_pipeline.c:158
#3  0x00007f0666d8abe4 in _tnl_draw_prims (ctx=0xb1e7d0, arrays=0xb5b540,
    prim=0xb59d24, nr_prims=1, ib=0x0, min_index=<value optimized out>,
    max_index=0) at tnl/t_draw.c:402
#4  0x00007f0666cdd1fc in brw_draw_prims (ctx=0xb1e7d0, arrays=0xb5b540,
    prim=0xb59d24, nr_prims=1, ib=0x0, min_index=0, max_index=0)
    at brw_draw.c:434
Comment 1 Michael Fu 2008-06-17 18:24:51 UTC 
dup of bug# 8724?
Comment 2 Roland Scheidegger 2008-06-17 18:43:10 UTC 
(In reply to comment #1)
> dup of bug# 8724?
Yes.

*** This bug has been marked as a duplicate of bug 8724 ***
Comment 3 Adam Jackson 2009-08-24 12:30:24 UTC 
Mass version move, cvs -> git

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.