public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jimis at gmx dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/49995] New: "operand missing mode" warning on sparc Date: Fri, 05 Aug 2011 21:17:00 -0000 [thread overview] Message-ID: <bug-49995-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49995 Summary: "operand missing mode" warning on sparc Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: jimis@gmx.net Host: sparc-unknown-linux-gnu I get the following warnings while building gcc on a sparcstation: build/genrecog ../../gcc-trunk-109439-co/gcc/config/sparc/sparc.md \ insn-conditions.md > tmp-recog.c ../../gcc-trunk-109439-co/gcc/config/sparc/sync.md:82: warning: operand 1 missing mode? ../../gcc-trunk-109439-co/gcc/config/sparc/sync.md:94: warning: operand 1 missing mode? The relevant lines of sync.md are: 82 (define_insn "*sync_compare_and_swap<mode>" 83 [(set (match_operand:I48MODE 0 "register_operand" "=r") 84 (mem:I48MODE (match_operand 1 "register_operand" "r"))) 85 (set (mem:I48MODE (match_dup 1)) 86 (unspec_volatile:I48MODE 87 [(match_operand:I48MODE 2 "register_operand" "r") 88 (match_operand:I48MODE 3 "register_operand" "0")] 89 UNSPECV_CAS))] 90 "TARGET_V9 && (<MODE>mode == SImode || TARGET_ARCH64)" 91 "cas<modesuffix>\t[%1], %2, %0" 92 [(set_attr "type" "multi")]) 93 94 (define_insn "*sync_compare_and_swapdi_v8plus" 95 [(set (match_operand:DI 0 "register_operand" "=h") 96 (mem:DI (match_operand 1 "register_operand" "r"))) 97 (set (mem:DI (match_dup 1)) 98 (unspec_volatile:DI 99 [(match_operand:DI 2 "register_operand" "h") 100 (match_operand:DI 3 "register_operand" "0")] 101 UNSPECV_CAS))] 102 "TARGET_V8PLUS"
next reply other threads:[~2011-08-05 21:17 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-05 21:17 jimis at gmx dot net [this message] 2011-08-05 22:18 ` [Bug target/49995] " dougmencken at gmail dot com 2011-08-07 18:54 ` ebotcazou 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-49995-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).