Bug 85586 - Draw module crashes in LLVM generated code since commit 60ec95fa1e0c42bd42358185970b20c9b81591fa
Summary: Draw module crashes in LLVM generated code since commit 60ec95fa1e0c42bd42358...
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-29 07:32 UTC by Michel Dänzer
Modified: 2016-01-20 02:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Michel Dänzer 2014-10-29 07:32:53 UTC
URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=60ec95fa1e0c42bd42358185970b20c9b81591fa

Author: Neil Roberts <neil@linux.intel.com>
Date:   Tue Sep 23 19:01:04 2014 +0100
 
mesa: Add support for the GL_KHR_context_flush_control extension

Since this commit, some piglit tests crash for me in the LLVM generated code called from draw_pt_fetch_shade_pipeline_llvm.c:370:

   if (fetch_info->linear)
      clipped = fpme->current_variant->jit_func( &fpme->llvm->jit_context,
                                       llvm_vert_info.verts,
                                       draw->pt.user.vbuffer,
                                       fetch_info->start,
                                       fetch_info->count,
                                       fpme->vertex_size,
                                       draw->pt.vertex_buffer,
                                       draw->instance_id,
                                       draw->start_index,
                                       draw->start_instance);

I can avoid the crashes with the environment variable DRAW_USE_LLVM=0.
Comment 1 Michel Dänzer 2014-10-29 07:34:58 UTC
Using current LLVM 3.6 Git snapshot.
Comment 2 Michel Dänzer 2016-01-20 02:52:24 UTC
I think this was fixed long ago.


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.