Hi,
"Kewen.Lin" writes:
> on 2023/10/25 16:14, Jiufu Guo wrote:
>>
>> Hi,
>>
>> "Kewen.Lin" writes:
>>
>>> Hi,
>>>
>>> on 2023/10/25 10:00, Jiufu Guo wrote:
Hi,
Sometimes, a complicated constant is built via 3(or more)
instructions to build. Generally speaking, it would
on 2023/10/25 16:14, Jiufu Guo wrote:
>
> Hi,
>
> "Kewen.Lin" writes:
>
>> Hi,
>>
>> on 2023/10/25 10:00, Jiufu Guo wrote:
>>> Hi,
>>>
>>> Sometimes, a complicated constant is built via 3(or more)
>>> instructions to build. Generally speaking, it would not be
>>> as faster as loading it from th
Hi,
"Kewen.Lin" writes:
> Hi,
>
> on 2023/10/25 10:00, Jiufu Guo wrote:
>> Hi,
>>
>> Sometimes, a complicated constant is built via 3(or more)
>> instructions to build. Generally speaking, it would not be
>> as faster as loading it from the constant pool (as a few
>> discussions in PR63281).
Hi,
on 2023/10/25 10:00, Jiufu Guo wrote:
> Hi,
>
> Sometimes, a complicated constant is built via 3(or more)
> instructions to build. Generally speaking, it would not be
> as faster as loading it from the constant pool (as a few
> discussions in PR63281).
I may miss some previous discussions, b
Hi,
Sometimes, a complicated constant is built via 3(or more)
instructions to build. Generally speaking, it would not be
as faster as loading it from the constant pool (as a few
discussions in PR63281).
For the concern that I raised in:
https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599676
