I don”t choose to run since I didn”t have issue run on my local simulator no matter qemu or spike.
So it”s better to check vsetvl asm.
full available is not consistent between LCM analysis and earliest fusion，so it”s safe to postpone it.
---- Replied Message ----
| From | Robin Dapp<rdapp....@gmail.com> |
| Date | 12/13/2023 20:08 |
| To | Juzhe-Zhong<juzhe.zh...@rivai.ai>, gcc-patches@gcc.gnu.org<gcc-patches@gcc.gnu.org> |
| Cc | rdapp....@gmail.com<rdapp....@gmail.com>, kito.ch...@gmail.com<kito.ch...@gmail.com>, kito.ch...@sifive.com<kito.ch...@sifive.com>, jeffreya...@gmail.com<jeffreya...@gmail.com> |
| Subject | Re: [PATCH] RISC-V: Postpone full available optimization [VSETVL PASS] |
Hi Juzhe,
in general looks OK to me.
Just a question for understanding:
> - if (header_info.valid_p ()
> - && (anticipated_exp_p (header_info) || block_info.full_available))
Why is full_available true if we cannot use it?
> +/* { dg-do compile } */
It would be nice if we could make this a run test as well.
Regards
Robin
in general looks OK to me.
Just a question for understanding:
> - if (header_info.valid_p ()
> - && (anticipated_exp_p (header_info) || block_info.full_available))
Why is full_available true if we cannot use it?
> +/* { dg-do compile } */
It would be nice if we could make this a run test as well.
Regards
Robin
