public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lasse.collin at tukaani dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111557] New: [RISC-V] The macro __riscv_unaligned_fast should be __riscv_misaligned_fast Date: Sat, 23 Sep 2023 19:31:09 +0000 [thread overview] Message-ID: <bug-111557-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111557 Bug ID: 111557 Summary: [RISC-V] The macro __riscv_unaligned_fast should be __riscv_misaligned_fast Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: lasse.collin at tukaani dot org Target Milestone: --- The RISC-V C API Specification[1] has __riscv_misaligned_fast, __riscv_misaligned_slow, and __riscv_misaligned_avoid. The commit 6e23440b [2] used "unaligned" instead of "misaligned" though. The spelling __riscv_unaligned_* was mentioned in [3] but in [4] it was changed to __riscv_misaligned_*. Clang doesn't have these macros yet but there is a recent pull request[5] that uses the __riscv_misaligned_* spelling. [1] https://github.com/riscv-non-isa/riscv-c-api-doc/blob/master/riscv-c-api.md [2] https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=6e23440b5df4011bbe1dbee74d47641125dd7d16 [3] https://github.com/riscv-non-isa/riscv-c-api-doc/issues/32 [4] https://github.com/riscv-non-isa/riscv-c-api-doc/pull/40 [5] https://github.com/llvm/llvm-project/pull/65756
next reply other threads:[~2023-09-23 19:31 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-23 19:31 lasse.collin at tukaani dot org [this message] 2023-11-16 18:27 ` [Bug target/111557] " cvs-commit at gcc dot gnu.org 2023-11-16 18:49 ` vineetg at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-111557-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).