public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "david.faust at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108790] New: bpf: gcc emits malformed ldxdw instruction at -O2 Date: Tue, 14 Feb 2023 18:52:23 +0000 [thread overview] Message-ID: <bug-108790-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108790 Bug ID: 108790 Summary: bpf: gcc emits malformed ldxdw instruction at -O2 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: david.faust at oracle dot com CC: cupertino.miranda at oracle dot com Target Milestone: --- Target: bpf With -O2 GCC emits a malformed ldxdw instruction in some cases: $ cat ldxdw.c unsigned long long test () { return *((unsigned long long *) 0x4000); } $ bpf-unknown-none-gcc -c -O2 ldxdw.c -o ldxdw.o /tmp/ccsuVj7l.s: Assembler messages: /tmp/ccsuVj7l.s:7: Error: unrecognized form of instruction `ldxdw %r0,16384' ldxdw (and all other {ldx,stx}{b,h,w,dw} insns should have a form like ldxdw %rX, [%rY + OFFSET] Looks like we need a better constraint on the memory operand in *mov<MM:mode>. Testing a patch for this now.
next reply other threads:[~2023-02-14 18:52 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-14 18:52 david.faust at oracle dot com [this message] 2023-02-14 22:47 ` [Bug target/108790] " cvs-commit at gcc dot gnu.org 2023-08-17 17:18 ` jemarch 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-108790-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).