| Summary: | Fix Vector extensions usage for GCC4 in fbmmx. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Stefan Dirsch <sndirsch> | ||||||
| Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | high | CC: | dberkholz, eich, plaes, roland.mainz | ||||||
| Version: | 6.8.2 | ||||||||
| Hardware: | Other | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
Stefan Dirsch
2005-04-03 22:55:48 UTC
Created attachment 2305 [details] [review] intrinsics-gcc4.patch Not required for HEAD. Comment on attachment 2305 [details] [review] intrinsics-gcc4.patch Maybe this would be something for the next bugfix release. Created attachment 2316 [details] [review] A different patch This patch is not conditionalized on gcc4 Comment on attachment 2305 [details] [review] intrinsics-gcc4.patch Setting "approval_X11R6.8.x"-flag to "request approval"(='?') ... Comment on attachment 2316 [details] [review] A different patch Requesting approval for my patch as well. My patch has the advantage that it doesn't conditionalize on gcc 4, so it is less likely to break across different compilers. *** Bug 2465 has been marked as a duplicate of this bug. *** Since it's fixed in CVS I think we can close this now. As far as I can see this has not been fixed for stable. > As far as I can see this has not been fixed for stable.
What is "stable"? CVS Head?
(In reply to comment #9) > As far as I can see this has not been fixed for stable. The approval flags are independent from the bug status (FIXED/CLOSED/REOPENED/EVIL666/etc.) ... the bug is fixed for Xorg trunk and the X11R6.8.x stable branch will follow once it's approved (hopefully this week) - no need to reopen it unless more patches should follow... Ok. The let's close it again. |
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.