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] New: Genrecog reports "source missing a mode?" for H8
Date: Tue, 28 Mar 2023 23:37:50 +0000 [thread overview]
Message-ID: <bug-109324-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109324
Bug ID: 109324
Summary: Genrecog reports "source missing a mode?" for H8
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: build
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jdx at o2 dot pl
Target Milestone: ---
Target: h8300-elf
Unfortunately, I barely understand .md files, but I think genrecog is a bit
overzealous. It would be nice if these warnings could be muted somehow.
build/genrecog.exe ../../../gcc/gcc/common.md
../../../gcc/gcc/config/h8300/h8300.md \
insn-conditions.md > tmp-recog.cc
../../../gcc/gcc/config/h8300/testcompare.md:29:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:29:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:55:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:64:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:73:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:82:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:82:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:82:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:98:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:106:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:114:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:122:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:130:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:151:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/jumpcall.md:290:1: warning: operand 0 missing
mode?
../../../gcc/gcc/config/h8300/jumpcall.md:290:1: warning: operand 0 missing
mode?
../../../gcc/gcc/config/h8300/jumpcall.md:327:1: warning: operand 1 missing
mode?
../../../gcc/gcc/config/h8300/jumpcall.md:327:1: warning: operand 1 missing
mode?
../../../gcc/gcc/config/h8300/jumpcall.md:360:1: warning: operand 0 missing
mode?
../../../gcc/gcc/config/h8300/jumpcall.md:360:1: warning: operand 0 missing
mode?
../../../gcc/gcc/config/h8300/jumpcall.md:397:1: warning: operand 1 missing
mode?
../../../gcc/gcc/config/h8300/jumpcall.md:397:1: warning: operand 1 missing
mode?
../../../gcc/gcc/config/h8300/testcompare.md:175:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:175:1: warning: source missing a
mode?
../../../gcc/gcc/config/h8300/testcompare.md:175:1: warning: source missing a
mode?
Statistics for recog:
Number of decisions: 3643
longest path: 76 (code: 597)
longest backtrack: 9 (code: 428)
Statistics for split_insns:
Number of decisions: 1409
longest path: 58 (code: 242)
longest backtrack: 4 (code: 199)
Statistics for peephole2_insns:
Number of decisions: 119
longest path: 69 (code: 8)
longest backtrack: 3 (code: 10)
Shared 3609 out of 7559 states by creating 1052 new states, saving 2557
next reply other threads:[~2023-03-28 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 23:37 jdx at o2 dot pl [this message]
2023-03-29 13:53 ` [Bug target/109324] " jakub at gcc dot gnu.org
2023-04-08 12:06 ` jdx at o2 dot pl
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@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).