Closed GoogleCodeExporter closed 8 years ago
That's odd. Neither iossim.m or iossim.gyp shows any recent change, so I wonder
how this can work for Chromium (or WebRTC for that matter, since we also build
ARM64, and use this library).
Can you provide details on exact reproduction steps? What version of Xcode do
you have?
+smut in case this is a known issue. Just disabling the warning in iossim.gyp
seems like the easiest solution (but has to be done in Chromium's src repo).
Original comment by kjellan...@google.com
on 19 Jan 2016 at 8:09
My local ios builds are working, for native 32 and 64 bit ARM, and Intel
simulator.
I'm on xcode 6.4 (6e35b)
Original comment by fbarch...@google.com
on 20 Jan 2016 at 12:24
OK. I don't know how old the version is on the bots, but I filed
https://code.google.com/p/chromium/issues/detail?id=579424 requesting upgrade
to Xcode 7, since that's what we have in WebRTC, and we don't hit this error.
Original comment by kjellan...@google.com
on 20 Jan 2016 at 8:42
Updating the bots didn't help
(https://code.google.com/p/chromium/issues/detail?id=579424).
I can take a look at bisecting the changes in the roll interval:
https://chromium.googlesource.com/chromium/src/+log/dad6346..70ee602b6
Something in there must have broken compilation.
Original comment by kjellander@chromium.org
on 21 Jan 2016 at 9:50
The following revision refers to this bug:
https://chromium.googlesource.com/libyuv/libyuv.git/+/a4288dd6dc59e34d2625ceff1cd72875b0c9b14f
commit a4288dd6dc59e34d2625ceff1cd72875b0c9b14f
Author: Henrik Kjellander <kjellander@webrtc.org>
Date: Thu Jan 21 12:07:35 2016
Disable sometimes-uninitialized Clang warning for iOS
This works around a compile problem with iossim.mm.
BUG=libyuv:548
TBR=fbarchard@chromium.org
Review URL: https://codereview.chromium.org/1611123004 .
[modify]
http://crrev.com/a4288dd6dc59e34d2625ceff1cd72875b0c9b14f/libyuv_test.gyp
Original comment by bugdroid1@chromium.org
on 21 Jan 2016 at 12:07
The workaround in #5 disables the warning. I don't know why we don't see the
same problem in WebRTC though (or Chromium for that matter).
Marking this as fixed since it is from libyuv's perspective at least.
Original comment by kjellan...@google.com
on 21 Jan 2016 at 12:08
Original issue reported on code.google.com by
fbarch...@google.com
on 19 Jan 2016 at 6:30