Bug 8392 - __GLX_ALIGN64 must be re-enabled on some architectures
Summary: __GLX_ALIGN64 must be re-enabled on some architectures
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Ext/GLX (show other bugs)
Version: 7.1 (2006.05)
Hardware: SPARC Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
: 5622 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-09-21 23:49 UTC by Jurij Smakov
Modified: 2008-07-07 04:11 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Proposed patch (1.62 KB, patch)
2006-09-21 23:52 UTC, Jurij Smakov
no flags Details | Splinter Review

Description Jurij Smakov 2006-09-21 23:49:53 UTC
Hi,

During the transition to the modular xorg, the logic setting the variable
__GLX_ALIGN64 on some arches was lost. As pointed out in
http://lists.freedesktop.org/archives/xorg/2006-September/018288.html it was
probably not intentional, as setting this variable activates the code taking
care of alignment issues. Without it the binaries might crash on the
architectures with strict alignment requirements. I have discovered this bug
while investigating the SIGBUS in xvfb on Debian sparc
(http://bugs.debian.org/388125).

Best regards,

Jurij Smakov
Comment 1 Jurij Smakov 2006-09-21 23:52:49 UTC
Created attachment 7116 [details] [review]
Proposed patch

This is a candidate patch for the problem. It re-enables __GLX_ALIGN64 on
arches where it was enabled in monolithic builds (according to imake/xmkmf's
xorg.cf). I've tested the xvfb built with this patch included, and it no longer
fails with SIGBUS. That was pretty much the only thing I tested, and did so on
sparc only.

Jurij.
Comment 2 Daniel Stone 2007-02-27 01:33:39 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 3 Michel Dänzer 2008-07-07 04:11:51 UTC
*** Bug 5622 has been marked as a duplicate of this bug. ***


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.