Re: [RFC] RISC-V: Implment H modifier for printing the next register name

2025-04-26 Thread Jeff Law
On 4/26/25 2:46 AM, Jin Ma wrote: On Sat, 26 Apr 2025 09:59:45 +0300, Dimitar Dimitrov wrote: On Fri, Apr 25, 2025 at 01:25:50PM +0800, Jin Ma wrote: For RV32 inline assembly, when handling 64-bit integer data, it is often necessary to process the lower and upper 32 bits separately. Unfortun

Re: [RFC] RISC-V: Implment H modifier for printing the next register name

2025-04-26 Thread Jin Ma
On Sat, 26 Apr 2025 09:59:45 +0300, Dimitar Dimitrov wrote: > On Fri, Apr 25, 2025 at 01:25:50PM +0800, Jin Ma wrote: > > For RV32 inline assembly, when handling 64-bit integer data, it is > > often necessary to process the lower and upper 32 bits separately. > > Unfortunately, we can only output t

Re: [RFC] RISC-V: Implment H modifier for printing the next register name

2025-04-26 Thread Dimitar Dimitrov
On Fri, Apr 25, 2025 at 01:25:50PM +0800, Jin Ma wrote: > For RV32 inline assembly, when handling 64-bit integer data, it is > often necessary to process the lower and upper 32 bits separately. > Unfortunately, we can only output the current register name > (lower 32 bits) but not the next register

[RFC] RISC-V: Implment H modifier for printing the next register name

2025-04-24 Thread Jin Ma
For RV32 inline assembly, when handling 64-bit integer data, it is often necessary to process the lower and upper 32 bits separately. Unfortunately, we can only output the current register name (lower 32 bits) but not the next register name (upper 32 bits). To address this, the modifier 'H' has be