| Server IP : 127.0.1.1 / Your IP : 216.73.216.172 Web Server : Apache/2.4.52 (Ubuntu) System : Linux bahcrestlinepropertiesllc 5.15.0-113-generic #123-Ubuntu SMP Mon Jun 10 08:16:17 UTC 2024 x86_64 User : www-data ( 33) PHP Version : 7.4.33 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /usr/lib/modules/5.15.0-113-generic/build/arch/arm/include/asm/ |
Upload File : |
/* SPDX-License-Identifier: GPL-2.0-only */ /* * linux/arch/arm/include/asm/neon.h * * Copyright (C) 2013 Linaro Ltd <ard.biesheuvel@linaro.org> */ #include <asm/hwcap.h> #define cpu_has_neon() (!!(elf_hwcap & HWCAP_NEON)) #ifdef __ARM_NEON__ /* * If you are affected by the BUILD_BUG below, it probably means that you are * using NEON code /and/ calling the kernel_neon_begin() function from the same * compilation unit. To prevent issues that may arise from GCC reordering or * generating(1) NEON instructions outside of these begin/end functions, the * only supported way of using NEON code in the kernel is by isolating it in a * separate compilation unit, and calling it from another unit from inside a * kernel_neon_begin/kernel_neon_end pair. * * (1) Current GCC (4.7) might generate NEON instructions at O3 level if * -mpfu=neon is set. */ #define kernel_neon_begin() \ BUILD_BUG_ON_MSG(1, "kernel_neon_begin() called from NEON code") #else void kernel_neon_begin(void); #endif void kernel_neon_end(void);