public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jdx at o2 dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109324] Genrecog reports "source missing a mode?" for H8
Date: Sat, 08 Apr 2023 12:06:55 +0000 [thread overview]
Message-ID: <bug-109324-4-ppIQ1rhgXZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109324-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109324
--- Comment #2 from Jan Dubiec <jdx at o2 dot pl> ---
It seems that msp430-elf has similar problem:
build/genrecog.exe ../../../gcc/gcc/common.md
../../../gcc/gcc/config/msp430/msp430.md \
insn-conditions.md > tmp-recog.cc
../../../gcc/gcc/config/msp430/msp430.md:204:1: warning: operand 0 missing
mode?
../../../gcc/gcc/config/msp430/msp430.md:241:1: warning: operand 0 missing
mode?
../../../gcc/gcc/config/msp430/msp430.md:453:1: warning: operand 2 missing
mode?
../../../gcc/gcc/config/msp430/msp430.md:1224:1: warning: operand 0 missing
mode?
../../../gcc/gcc/config/msp430/msp430.md:1241:1: warning: operand 1 missing
mode?
../../../gcc/gcc/config/msp430/msp430.md:1294:1: warning: operand 0 missing
mode?
../../../gcc/gcc/config/msp430/msp430.md:1602:1: warning: operand 0 missing
mode?
../../../gcc/gcc/config/msp430/msp430.md:1612:1: warning: operand 0 missing
mode?
Statistics for recog:
Number of decisions: 629
longest path: 32 (code: 2)
longest backtrack: 4 (code: 66)
Statistics for split_insns:
Number of decisions: 15
longest path: 10 (code: 1)
longest backtrack: 1 (code: 2)
Statistics for peephole2_insns:
Number of decisions: 13
longest path: 13 (code: 1)
longest backtrack: 0 (code: 1)
Shared 363 out of 1138 states by creating 118 new states, saving 245
next prev parent reply other threads:[~2023-04-08 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 23:37 [Bug target/109324] New: " jdx at o2 dot pl
2023-03-29 13:53 ` [Bug target/109324] " jakub at gcc dot gnu.org
2023-04-08 12:06 ` jdx at o2 dot pl [this message]
2023-04-08 22:14 ` 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-109324-4-ppIQ1rhgXZ@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: link
Be 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).