|
From: | Piotr Stanczyk |
Subject: | Re: [Openexr-user] [Openexr-devel] Optimisation code path for reading images |
Date: | Tue, 18 Jun 2013 16:15:52 +0000 |
Is this something that was quite deterministic in behaviour?
(Does anyone have an example of a corrupted image?) - Piotr
From: Juri Abramov address@hidden
Sent: 18 June 2013 09:13 To: Halfdan Ingvarsson; Piotr Stanczyk Cc: address@hidden; address@hidden Subject: RE: [Openexr-devel] Optimisation code path for reading images Hi Halfdan,
Yep, we ran into this one too. Was already the case for OpenEXR 1.6/1.7. Would be good to know if it is fixed in 4.5.
Juri
From: openexr-devel-bounces+address@hidden
[mailto:openexr-devel-bounces+address@hidden On Behalf Of
Halfdan Ingvarsson
Also, compiling the EXR2.0 library using gcc 4.2/4.3/4.4 with -O3 results in the PIZ compression code producing occasional garbage data (-O3 is the default for cmake release builds). The workaround was to build with -O2. gcc 4.6 and up
seem ok. I didn't test with gcc 4.5.
This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
|
[Prev in Thread] | Current Thread | [Next in Thread] |