Summary: | compiler/test_eu_compact failure with GCC 8 | ||
---|---|---|---|
Product: | Mesa | Reporter: | Vinson Lee <vlee> |
Component: | Other | Assignee: | mesa-dev |
Status: | RESOLVED FIXED | QA Contact: | mesa-dev |
Severity: | normal | ||
Priority: | medium | CC: | currojerez |
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | 0001-intel-ir-Fix-invalid-type-aliasing-with-undefined-be.patch |
Description
Vinson Lee
2018-02-12 08:34:03 UTC
Bugs with unreleased versions of GCC cannot block a Mesa release. Created attachment 137473 [details] [review] 0001-intel-ir-Fix-invalid-type-aliasing-with-undefined-be.patch Does it go away with the attached patch? I had it in a branch that was making some unrelated changes which just happened to affect the order instructions are emitted by GCC in the test_fuzz_compact_instruction() function, causing the bit twiddling to be done after the clear_pad_bits() call which modifies the same data through a pointer of different type, leading to undefined behavior. I had seen this happen on GCC 7. (In reply to Francisco Jerez from comment #2) > Created attachment 137473 [details] [review] [review] > 0001-intel-ir-Fix-invalid-type-aliasing-with-undefined-be.patch > > Does it go away with the attached patch? I had it in a branch that was > making some unrelated changes which just happened to affect the order > instructions are emitted by GCC in the test_fuzz_compact_instruction() > function, causing the bit twiddling to be done after the clear_pad_bits() > call which modifies the same data through a pointer of different type, > leading to undefined behavior. I had seen this happen on GCC 7. attachment 137473 [details] [review] fixes the test_eu_compact failure with GCC 8. Tested-by: Vinson Lee <vlee@freedesktop.org> Thanks, should be fixed in master now. |
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.