-
Notifications
You must be signed in to change notification settings - Fork 18.7k
Closed
Closed
Copy link
Labels
NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.QuestionIssues that are questions about using Go.Issues that are questions about using Go.WaitingForInfoIssue is not actionable because of missing required information, which needs to be provided.Issue is not actionable because of missing required information, which needs to be provided.arch-riscvIssues solely affecting the riscv64 architecture.Issues solely affecting the riscv64 architecture.compiler/runtimeIssues related to the Go compiler and/or runtime.Issues related to the Go compiler and/or runtime.
Milestone
Description
Currently Golang supports a few RISCV-V profiles. Just looking at RVA20U64, it supports the Zicclsm extension which allows for unaligned accesses.
Is there a clarifying document on whether unaligned stores and loads are classified as bugs for the golang compiler?
One reference that points towards this is the replies in this thread: https://groups.google.com/g/golang-dev/c/5Om3lJcYxzA/m/UyhzduXTBgAJ?utm_medium=email&utm_source=footer
Metadata
Metadata
Assignees
Labels
NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.QuestionIssues that are questions about using Go.Issues that are questions about using Go.WaitingForInfoIssue is not actionable because of missing required information, which needs to be provided.Issue is not actionable because of missing required information, which needs to be provided.arch-riscvIssues solely affecting the riscv64 architecture.Issues solely affecting the riscv64 architecture.compiler/runtimeIssues related to the Go compiler and/or runtime.Issues related to the Go compiler and/or runtime.