llvm.prefetch fails code generation on Linux.

[Kelimion]

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• Operating System: Ubuntu 20.04
• Please paste odin version output: odin version dev-2021-09:5f920414

Expected Behavior

Example prints "Foozle prefetched."

Current Behavior

Code generation error on Linux. Example works on Windows.

LLVM CODE GEN FAILED FOR PROCEDURE: test.prefetch_address
; Function Attrs: alwaysinline
define internal void @test.prefetch_address(i8* %0, i8* noalias nocapture nonnull %__.context_ptr) #0 {
decls:
  %1 = alloca i8*, align 8
  br label %entry

entry:                                            ; preds = %decls
  store i8* %0, i8** %1, align 8
  %2 = bitcast i8* %__.context_ptr to %runtime.Context*
  %3 = load i8*, i8** %1, align 8
  call void @llvm.prefetch(i8* %3, i32 0, i32 3, i32 1) #0
  ret void
}

Intrinsic name not mangled correctly for type arguments! Should be: llvm.prefetch.p0i8
void (i8*, i32, i32, i32)* @llvm.prefetch

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

odin run .

package test

import "core:sys/llvm"
import "core:fmt"

prefetch_address :: #force_inline proc(address: rawptr) {
    llvm.prefetch(address, .Read, .High, .Data)
}
prefetch_offset  :: #force_inline proc(address: rawptr, auto_cast offset: uintptr) {
    ptr := rawptr(uintptr(address) + offset)
    prefetch_address(ptr)
}

prefetch :: proc { prefetch_address, prefetch_offset, }

main :: proc() {
    foozle: u64
    prefetch(&foozle)
    fmt.println("Foozle prefetched.")
}

[github-actions]

Hello!

I am marking this issue as stale as it has not received any engagement from the community or maintainers 120 days. That does not imply that the issue has no merit! If you feel strongly about this issue

• open a PR referencing and resolving the issue;
• leave a comment on it and discuss ideas how you could contribute towards resolving it;
• leave a comment and describe in detail why this issue is critical for your use case;
• open a new issue with updated details and a plan on resolving the issue.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone..