On Thu, 2024-07-18 at 20:41 +0800, Xi Ruoyao wrote:
> On Thu, 2024-07-18 at 19:54 +0800, Xi Ruoyao wrote:
> > On Tue, 2024-07-09 at 22:29 -0600, Jeff Law wrote:
> > >
> > >
> > > On 7/9/24 8:35 PM, Xi Ruoyao wrote:
> > > > On Mon, 2024-07-08 at 15:03 -0600, Jeff Law wrote:
> > > > > So I would us
On Thu, 2024-07-18 at 19:54 +0800, Xi Ruoyao wrote:
> On Tue, 2024-07-09 at 22:29 -0600, Jeff Law wrote:
> >
> >
> > On 7/9/24 8:35 PM, Xi Ruoyao wrote:
> > > On Mon, 2024-07-08 at 15:03 -0600, Jeff Law wrote:
> > > > So I would use tmp (or another word_mode pseudo register) for the
> > > > desti
On Tue, 2024-07-09 at 22:29 -0600, Jeff Law wrote:
>
>
> On 7/9/24 8:35 PM, Xi Ruoyao wrote:
> > On Mon, 2024-07-08 at 15:03 -0600, Jeff Law wrote:
> > > So I would use tmp (or another word_mode pseudo register) for the
> > > destination of that emit_insn. Then something like:
> > >
> > >
On Tue, 2024-07-09 at 20:21 -0600, Jeff Law wrote:
>
>
> On 7/9/24 8:14 PM, Xi Ruoyao wrote:
> > On Tue, 2024-07-09 at 16:10 -0700, Vineet Gupta wrote:
> > > On 7/3/24 21:35, Xi Ruoyao wrote:
> > > > On Sun, 2024-06-30 at 17:47 -0700, Vineet Gupta wrote:
> > > > > - Don't hardcode SI in patter
On 7/9/24 8:35 PM, Xi Ruoyao wrote:
On Mon, 2024-07-08 at 15:03 -0600, Jeff Law wrote:
So I would use tmp (or another word_mode pseudo register) for the
destination of that emit_insn. Then something like:
t = gen_lowpart (SImode, tmp);
SUBREG_PROMOTED_VAR_P (tmp) = 1;
On Mon, 2024-07-08 at 15:03 -0600, Jeff Law wrote:
> So I would use tmp (or another word_mode pseudo register) for the
> destination of that emit_insn. Then something like:
>
> t = gen_lowpart (SImode, tmp);
> SUBREG_PROMOTED_VAR_P (tmp) = 1;
> SUBREG_PROMOTED_SET (tmp, SRP
On 7/9/24 8:14 PM, Xi Ruoyao wrote:
On Tue, 2024-07-09 at 16:10 -0700, Vineet Gupta wrote:
On 7/3/24 21:35, Xi Ruoyao wrote:
On Sun, 2024-06-30 at 17:47 -0700, Vineet Gupta wrote:
- Don't hardcode SI in patterns, try to keep X to avoid potential
sign extension pitfalls. Implementati
On Tue, 2024-07-09 at 16:10 -0700, Vineet Gupta wrote:
> On 7/3/24 21:35, Xi Ruoyao wrote:
> > On Sun, 2024-06-30 at 17:47 -0700, Vineet Gupta wrote:
> > > - Don't hardcode SI in patterns, try to keep X to avoid potential
> > > sign extension pitfalls. Implementation wise requires skipping
>
Hi,
在 2024/7/10 8:04, Vineet Gupta 写道:
> So it seems initial versions of the patch didn't specify anything about
> output mode. Richi asked for it in review and in v4 Hao added it.
> But I don't see anyone asking specifically for SImode.
> I guess that can be relaxed. Hao do you have any inputs he
+CC Hao Chen Gui
On 7/9/24 16:21, Jeff Law wrote:
- Don't hardcode SI in patterns, try to keep X to avoid potential
sign extension pitfalls. Implementation wise requires skipping
:MODE specifier in match_operand which is flagged as missing mode
warning.
>>> I'
On 7/9/24 5:10 PM, Vineet Gupta wrote:
On 7/3/24 21:35, Xi Ruoyao wrote:
On Sun, 2024-06-30 at 17:47 -0700, Vineet Gupta wrote:
- Don't hardcode SI in patterns, try to keep X to avoid potential
sign extension pitfalls. Implementation wise requires skipping
:MODE specifier in mat
On 7/3/24 21:35, Xi Ruoyao wrote:
> On Sun, 2024-06-30 at 17:47 -0700, Vineet Gupta wrote:
>> - Don't hardcode SI in patterns, try to keep X to avoid potential
>> sign extension pitfalls. Implementation wise requires skipping
>> :MODE specifier in match_operand which is flagged as missing
On 7/8/24 14:03, Jeff Law wrote:
>
> On 6/30/24 6:47 PM, Vineet Gupta wrote:
>> Changes since v1:
>>- Removed UNSPEC_{INFINITE,ISNORMAL}
>>- Don't hardcode SI in patterns, try to keep X to avoid potential
>> sign extension pitfalls. Implementation wise requires skipping
>> :MODE s
On 6/30/24 6:47 PM, Vineet Gupta wrote:
Changes since v1:
- Removed UNSPEC_{INFINITE,ISNORMAL}
- Don't hardcode SI in patterns, try to keep X to avoid potential
sign extension pitfalls. Implementation wise requires skipping
:MODE specifier in match_operand which is flagged as m
On Sun, 2024-06-30 at 17:47 -0700, Vineet Gupta wrote:
> - Don't hardcode SI in patterns, try to keep X to avoid potential
> sign extension pitfalls. Implementation wise requires skipping
> :MODE specifier in match_operand which is flagged as missing mode
> warning.
I'm unsure about
Changes since v1:
- Removed UNSPEC_{INFINITE,ISNORMAL}
- Don't hardcode SI in patterns, try to keep X to avoid potential
sign extension pitfalls. Implementation wise requires skipping
:MODE specifier in match_operand which is flagged as missing mode
warning.
---
Currently isfinite
16 matches
Mail list logo
