RISC-V: Add type attribute in *<optab>_not_const<mode> pattern
Checks
Commit Message
After f088b768d01a commit riscv_sched_variable_issue function requires
that all insns should have a type attribute.
When I sent my previous patch there was no such limitation.
Currently, I have regressions on my tests. This patch fixes them.
gcc/ChangeLog:
* config/riscv/bitmanip.md (*<optab>_not_const<mode>): Added type
attribute
Comments
On 9/29/23 16:53, Jivan Hakobyan wrote:
> After f088b768d01a commit riscv_sched_variable_issue function requires
> that all insns should have a type attribute.
>
> When I sent my previous patch there was no such limitation.
> Currently, I have regressions on my tests. This patch fixes them.
>
> gcc/ChangeLog:
> * config/riscv/bitmanip.md (*<optab>_not_const<mode>): Added
> type attribute
I should have remembered that we've got a policy that all insns need a
type. My bad.
Pushed to the trunk,
jeff
@@ -225,7 +225,9 @@ (define_insn_and_split "*<optab>_not_const<mode>"
"#"
"&& reload_completed"
[(set (match_dup 3) (match_dup 2))
- (set (match_dup 0) (bitmanip_bitwise:X (not:X (match_dup 1)) (match_dup 3)))])
+ (set (match_dup 0) (bitmanip_bitwise:X (not:X (match_dup 1)) (match_dup 3)))]
+ ""
+ [(set_attr "type" "bitmanip")])
;; '(a >= 0) ? b : 0' is emitted branchless (from if-conversion). Without a
;; bit of extra help for combine (i.e., the below split), we end up emitting