Displaying 3 results from an estimated 3 matches for "per_002dobject".
2014 Jul 29
2
1.21 vs 1.3 encoding speed
Miroslav Lichvar wrote:
> Well, this reverts the commit 18e0154. How is the user supposed to set
> CFLAGS without getting -O3 -funroll-loops there? (e.g. to minimize the
> size of the compiled binaries)
Is it -O3 or -funroll-loops that you have a problem with? Or both?
What would you prefer to see as the default optimisation level?
I'm sure there is a solution to this. Lets find
2014 Nov 28
2
[RFC PATCHv1] armv7: celt_pitch_xcorr: Introduce ARM neon intrinsics
Review comments inline.
> +if OPUS_ARM_NEON_INTR
> +noinst_LTLIBRARIES = libarmneon.la
> +libarmneon_la_SOURCES = $(CELT_SOURCES_ARM_NEON_INTR)
> +libarmneon_la_CPPFLAGS = $(OPUS_ARM_NEON_INTR_CPPFLAGS) -I$(top_srcdir)/include
> +endif
I don't think these should be in a separate library. It brings with it
lots of complications (to name one: wouldn't the .pc files need to
2014 Dec 01
0
[RFC PATCHv1] armv7: celt_pitch_xcorr: Introduce ARM neon intrinsics
...ase use the same mechanism that the SSE intrinsics use to
> add CFLAGS to the compilation of specific object files, e.g.,
Sorry, I don't know what .pc file is. Also no strong opinions on my
side.. but I was merely following
guidance from
http://www.gnu.org/software/automake/manual/html_node/Per_002dObject-Flags.html
which specifically advocates against per object flags.
I can follow your feedback if you still think per-object flag is the
right thing to do for libopus.
Please let me know either way.
>
> $(SSE_OBJ): CFLAGS += -msse4.1
>
>> +void (*const CELT_PITCH_XCORR_IMPL[OPUS_ARCH...