Bug 102466 - gallium/auxiliary/util/u_cpu_detect.c: 2 * bad condition ?
Summary: gallium/auxiliary/util/u_cpu_detect.c: 2 * bad condition ?
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: 17.2
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-29 10:39 UTC by dcb314
Modified: 2019-09-18 20:26 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description dcb314 2017-08-29 10:39:08 UTC
1.

mesa-17.1.8/src/gallium/auxiliary/util/u_cpu_detect.c:370]: (style) Condition '(xgetbv()&6)==6' is always false

Source code is

          ((xgetbv() & 6) == 6);    // XMM & YMM

2.

mesa-17.1.8/src/gallium/auxiliary/util/u_cpu_detect.c:394]: (style) Condition '(xgetbv()&6)==6' is always false

Duplicate
Comment 1 Gert Wollny 2017-08-29 11:04:43 UTC
It would be helpful to add on which OS and with which compiler and for what architecture you were compiling mesa, because depending on the build environment xgetbv() may simply return 0 as a fallback (see lines 259-277 in the same file).
Comment 2 dcb314 2017-08-29 11:38:46 UTC
(In reply to Gert Wollny from comment #1)
> It would be helpful to add on which OS and with which compiler and for what
> architecture you were compiling mesa, because depending on the build
> environment xgetbv() may simply return 0 as a fallback (see lines 259-277 in
> the same file).

I think you missed the point. Any expression ANDed with 6 will be != 6.

OS, compiler and arch independent. For the record, Linux, gcc and x86_64,
although I used a static analyser called cppcheck to find this bug.
Comment 3 Emil Velikov 2017-08-29 12:22:52 UTC
(In reply to dcb314 from comment #2)

> I think you missed the point. Any expression ANDed with 6 will be != 6.
> 
How about when xgetbv() returns say 6 or 7 (amongst others)?

Also keep in mind that the file depends on multiple defines. Based on a _very_ old play with Mesa + cppcheck, the latter was tripping quite often, producing false positives.

The OS/compiler request does not sound that unreasonable ;-)
Comment 4 GitLab Migration User 2019-09-18 20:26:38 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1017.


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.