Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

__builtin_neon_vld1q_v() won't accept 64-bit (unsigned long *) on aarch64 #19266

Closed
llvmbot opened this issue Feb 19, 2014 · 1 comment
Closed

__builtin_neon_vld1q_v() won't accept 64-bit (unsigned long *) on aarch64 #19266

llvmbot opened this issue Feb 19, 2014 · 1 comment
Labels
bugzilla Issues migrated from bugzilla clang Clang issues not falling into any other category worksforme Resolved as "works for me"

Comments

@llvmbot
Copy link
Collaborator

llvmbot commented Feb 19, 2014

Bugzilla Link 18892
Resolution WORKSFORME
Resolved on Jan 23, 2019 23:48
Version trunk
OS Linux
Reporter LLVM Bugzilla Contributor
CC @nickdesaulniers

Extended Description

clang --target=aarch64-linux-gnu -xc -c - << EOF
#include <arm_neon.h>
void fn(unsigned long *p, uint64x2_t v) { vst1q_u64(p, v); }
EOF

gives me:
:2:54: warning: incompatible pointer types assigning to 'unsigned long long *' from 'unsigned long *' [-Wincompatible-pointer-types]

Changing the pointer type to long long fixes things; unfortunately my /usr/aarch64-linux-gnu/include/stdint.h has uint64_t as simply unsigned long.
@llvmbot
Copy link
Collaborator Author

llvmbot commented May 14, 2014

Seems to be fixed already (doesn't reproduce with trunk r208757). Tested both the ARM64 and AArch64 backend.

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 9, 2021
@Quuxplusone Quuxplusone added the worksforme Resolved as "works for me" label Jan 20, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugzilla Issues migrated from bugzilla clang Clang issues not falling into any other category worksforme Resolved as "works for me"
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Quuxplusone @llvmbot