Summary: | sparc64 is not properly detected as 64 bit due to incorrect architecture mapping | ||
---|---|---|---|
Product: | PulseAudio | Reporter: | John Paul Adrian Glaubitz <glaubitz> |
Component: | core | Assignee: | pulseaudio-bugs |
Status: | RESOLVED FIXED | QA Contact: | pulseaudio-bugs |
Severity: | normal | ||
Priority: | medium | CC: | brian.cameron, lennart |
Version: | unspecified | ||
Hardware: | SPARC | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | [PATCH] pulsecore: Fix incorrect architecture mapping on sparc64. |
Description
John Paul Adrian Glaubitz
2016-05-16 19:03:12 UTC
Comment on attachment 123794 [details] [review] [PATCH] pulsecore: Fix incorrect architecture mapping on sparc64. Review of attachment 123794 [details] [review]: ----------------------------------------------------------------- ::: src/pulsecore/atomic.h @@ +201,4 @@ > > return (v); > } > +#elif defined(__sparc__) && defined(__arch64__) I'm wondering if we might break some other/older compiler with this change. Any way to verify this? CC'ing Brian Cameron Brian, not sure if you're still involved in any of this -- comments? (In reply to Arun Raghavan from comment #1) > I'm wondering if we might break some other/older compiler with this change. > Any way to verify this? Very unlikely. According to David Miller, the definition "sparc64" was never valid [1]. For reference, David Miller has been the primary person behind the SPARC port of the Linux kernel since the 90ies [2]. Cheers, Adrian > [1] http://marc.info/?l=linux-sparc&m=146341133910751&w=2 > [2] https://en.wikipedia.org/wiki/David_S._Miller Oh, and we fixed the same issue already in systemd [1].
Adrian
> [1] https://github.com/systemd/systemd/commit/cd042078df2151d7824abf91107a0d4a8716e54f
Fair enough, I've pushed this out to next now (so it'll be in PA 10.0). (In reply to Arun Raghavan from comment #5) > Fair enough, I've pushed this out to next now (so it'll be in PA 10.0). Thank you :). |
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.