Closed GoogleCodeExporter closed 9 years ago
Original comment by jz...@google.com
on 23 Jan 2015 at 4:08
As small request. Would be possible to reflect in ./configure's output, that
use-x86inc was enabled or disabled? For example here it was enabled:
Configuring selected codecs
enabling vp8_encoder
enabling vp8_decoder
enabling vp9_encoder
enabling vp9_decoder
Configuring for target 'x86-linux-gcc'
enabling x86
enabling pic
enabling runtime_cpu_detect
enabling mmx
enabling sse
enabling sse2
enabling sse3
enabling ssse3
enabling sse4_1
enabling avx
enabling avx2
using yasm
enabling postproc
enabling webm_io
enabling libyuv
Creating makefiles for x86-linux-gcc libs
Creating makefiles for x86-linux-gcc docs
Then I've looked at generated files in source directory and I was sure that
configure option actually worked.
Original comment by mikolaj....@gmail.com
on 28 Jan 2015 at 2:52
> As small request. Would be possible to reflect in ./configure's output, that
> use-x86inc was enabled or disabled? For example here it was enabled:
> [...]
Seems reasonable. I opened #936 to track.
[1] https://code.google.com/p/webm/issues/detail?id=936
Original comment by jz...@google.com
on 29 Jan 2015 at 4:27
Original comment by fgalli...@google.com
on 30 Jan 2015 at 8:37
Issue 924 was resolved.
https://code.google.com/p/webm/issues/detail?id=924
Original comment by yunqingw...@google.com
on 30 Jan 2015 at 8:41
I'm compiling libvpx commit be6aeada and I see "#define CONFIG_USE_X86INC 0"
after configure. Do you think can --disable-use-x86inc as default for OpenBSD
be reverted?
Original comment by mikolaj....@gmail.com
on 31 Jan 2015 at 9:23
This has been merged.
3be948d Merge "configure: enable x86inc for all intel platforms"
769fe6e configure: enable x86inc for all intel platforms
All issues related to this bug should be addressed now. There are still some
issues with building in general (unit tests with clang++ and bad sse2
intrinsics causing failure with gcc), but those can go in new bugs.
Thanks again for the report and the help in working through this.
Original comment by jz...@google.com
on 5 Feb 2015 at 8:22
Original issue reported on code.google.com by
brad.ope...@gmail.com
on 10 Jun 2014 at 3:20