From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 321] New: BUG: Running ltp on a pipeline gives warnings about loops
Date: Mon, 18 May 2020 15:21:33 +0000
Message-ID: <bug-321-13@https.bugs.libre-soc.org/> (raw)
https://bugs.libre-soc.org/show_bug.cgi?id=321
Bug ID: 321
Summary: BUG: Running ltp on a pipeline gives warnings about
loops
Product: Libre-SOC's first SoC
Version: unspecified
Hardware: PC
OS: Windows
Status: CONFIRMED
Severity: normal
Priority: ---
Component: Source Code
Assignee: lkcl@lkcl.net
Reporter: mtnolan2640@gmail.com
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
Created attachment 55
--> https://bugs.libre-soc.org/attachment.cgi?id=55&action=edit
Photo of loop in yosys graph
Running `ltp` in yosys on a pipeline gives many warnings about loops being
detected. For instance, running yosys -p `read_ilang logical_pipeline.il;
synth; ltp` in soc/fu/logical/test gives the following output:
yosys> ltp
3. Executing LTP pass (find longest path).
Longest topological path in input (length=4):
0: \op__input_carry [1]
1: $abc$6362$new_n198_ (via
$abc$6362$auto$blifparse.cc:377:parse_blif$6427)
2: $abc$6362$new_n199_ (via
$abc$6362$auto$blifparse.cc:377:parse_blif$6428)
3: $abc$6362$new_n201_ (via
$abc$6362$auto$blifparse.cc:377:parse_blif$6430)
4: \carry_in$25 (via $abc$6362$auto$blifparse.cc:377:parse_blif$6432)
Longest topological path in output (length=9):
0: \stage_o [63]
<snip>
9: \cr0$24 [3] (via $abc$8116$auto$blifparse.cc:377:parse_blif$8261)
Longest topological path in main (length=34):
0: \op__insn_type [5]
<snip>
34: \stage_o [5] (via $abc$6433$auto$blifparse.cc:377:parse_blif$7943)
Longest topological path in countz (length=27):
0: \rs_i [47]
<snip>
27: \result_o [0] (via $abc$6123$auto$blifparse.cc:377:parse_blif$6352)
Warning: Detected loop at \stage_o$next [63] in pipe
Warning: Detected loop at \stage_o$next [62] in pipe
Warning: Detected loop at \stage_o$next [61] in pipe
Warning: Detected loop at \stage_o$next [60] in pipe
<snip>
Warning: Detected loop at \stage_o$next [0] in pipe
Warning: Detected loop at \so$23$next in pipe
Warning: Detected loop at \r_busy$next in pipe
Warning: Detected loop at \op__insn$20$next [31] in pipe
Warning: Detected loop at \op__insn$20$next [30] in pipe
Warning: Detected loop at \op__insn$20$next [29] in pipe
Warning: Detected loop at \op__insn$20$next [28] in pipe
...
Graphing the module (show pipe) shows a couple of loops in the top level pipe
object, outside of the stages
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next reply index
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 15:21 bugzilla-daemon [this message]
2020-05-18 15:57 ` [libre-riscv-dev] [Bug 321] " bugzilla-daemon
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-321-13@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git