Bug 6077 - lrint[f] broken on ARM
Summary: lrint[f] broken on ARM
Status: RESOLVED NOTOURBUG
Alias: None
Product: liboil
Classification: Unclassified
Component: unknown (show other bugs)
Version: HEAD
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: David Schleef
QA Contact: David Schleef
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-01 19:39 UTC by Grzegorz Dąbrowski
Modified: 2006-05-18 21:31 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Grzegorz Dąbrowski 2006-03-01 19:39:15 UTC
I got this under scratchbox, ARM (qemu)

[sbox-arm: ~] > gst-inspect
OIL: ERROR liboilprofile.c 300: _oil_profile_init(): Using gettimeofday() as a
timestamp function.  Please add a timestamp function for your platform.
OIL: ERROR liboiltest.c 403: oil_test_check_impl(): function conv_u16_f32_lrintf
in class conv_u16_f32 failed check (1.57279e+06 > 0.1) || (outside=0)
OIL: ERROR liboiltest.c 403: oil_test_check_impl(): function conv_u16_f32_lrint
in class conv_u16_f32 failed check (1.57279e+06 > 0.1) || (outside=0)
OIL: ERROR liboiltest.c 403: oil_test_check_impl(): function conv_u8_f32_lrintf
in class conv_u8_f32 failed check (5315 > 0.1) || (outside=0)
OIL: ERROR liboiltest.c 403: oil_test_check_impl(): function conv_u8_f32_lrint
in class conv_u8_f32 failed check (5315 > 0.1) || (outside=0)
Comment 1 David Schleef 2006-03-21 09:26:34 UTC
I removed the gettimeofday warning, as it's known that ARM processors made by
ARM don't have a timestamping instruction.  Changing title appropriately.

What libc are you using?
Comment 2 Grzegorz Dąbrowski 2006-03-21 19:08:48 UTC
I'm using glibc-2.3.2 with debian patches
(http://scratchbox.org/download/files/sbox-files/)
Comment 3 Grzegorz Dąbrowski 2006-03-21 21:06:19 UTC
But on glibc from http://www.codesourcery.com toolchain (this is 2.3.6+, maybe
2.4-pre) the problem doesn't exist.
Comment 4 David Schleef 2006-05-19 14:31:21 UTC
Ok, this is a (fixed) bug in glibc.


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.