Set neon flags for webOS

[cscd98]

Set some optional? performance flags.

[notaz]

HAVE_NEON_ASM is 32-bit only and will break arm64 build, but from quick googling it seems there are arm64 webos devices. Also it should be autodetected anyway, so I think you can just leave it out.

[notaz]

Turns out HAVE_NEON is unused so I've cleaned it up. I think all source-level optimizations should get enabled as long as you have the right CFLAGS or your toolchain has them preconfigured and patches like this are not needed.

[cscd98]

I wish there was 64-bit webOS TVs but there is none at present.

webOS TVs are 32-bit userspace on a 64-bit linux kernel. All the libretro cores are compiled for 32-bit for this platform (should that change, I will have quite a time updating them!).

HAVE_NEON_ASM is unset so the neon optimized code is unused.

I've updated my PR which should exclude aarch64:

# webOS
ifneq (,$(findstring webos,$(CROSS_COMPILE)$(findstring starfish,$(CROSS_COMPILE))))
	ifeq (,$(findstring aarch64,$(CROSS_COMPILE)))
		HAVE_NEON_ASM = 1
		BUILTIN_GPU = neon
	endif
endif

I think I might start using this from now on for other cores.

Is the neon path compatible with softfp?

[notaz]

HAVE_NEON_ASM is unset so the neon optimized code is unused.

Your CFLAGS might be missing -mfpu=neon or something, Makefile.libretro has this and it should detect it:

ifndef HAVE_NEON_ASM
HAVE_NEON_ASM = $(shell $(CC) -E -dD $(CFLAGS) include/arm_features.h | grep -q HAVE_NEON32 && echo 1 || echo 0)
endif

Is the neon path compatible with softfp?

Yes, it's what it was written for. Shouldn't matter in practice as standard float isn't used anywhere.

[cscd98]

Ah that explains it. It works, thanks