public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106632] New: undefined code causes assembler failure Date: Mon, 15 Aug 2022 22:56:09 +0000 [thread overview] Message-ID: <bug-106632-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106632 Bug ID: 106632 Summary: undefined code causes assembler failure Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: assemble-failure Severity: normal Priority: P3 Component: target Assignee: pinskia at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- Target: riscv-linux-gnu Take: long f(long a, long b) { b = 66; return (a >> b) & 1; } This will produce: f: bexti a0,a0,66 ret Which is invalid assembly as rejected by gas: /tmp/ccTvKnLv.s: Assembler messages: /tmp/ccTvKnLv.s:8: Error: improper shift amount (66)
next reply other threads:[~2022-08-15 22:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-15 22:56 pinskia at gcc dot gnu.org [this message] 2022-08-15 22:57 ` [Bug target/106632] " pinskia at gcc dot gnu.org 2022-08-24 19:20 ` cvs-commit at gcc dot gnu.org 2022-08-24 19:21 ` pinskia 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-106632-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).