Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: sergos <sergos@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit] Fix FOLD rule for strength reduction of widening.
Date: Fri, 29 Oct 2021 10:49:15 +0300	[thread overview]
Message-ID: <YXune+a3cnrGFQat@root> (raw)
In-Reply-To: <E2489123-3FCD-4CB2-BB19-3EEA85D57550@tarantool.org>

Hi!

On 28.10.21, sergos wrote:
> Hi! 
> 
> The description looks good!
> 
> Although, I can’t get the point how this
> 
> > (negative offset from the stack
> > pointer may appear positive and result is undefined memory access). 
> 
> can’t be applied to a constant? Hence, we’d need a check?
> 
> >> Should it check if integer - even a constant one - is positive? 
> > 
> > No, why? In fold rule are declared both types: INT64 and UINT64.

Sorry, misinterpreted your question here.
Yes, there is the check
| lo && IR(lo)->o == IR_KINT && IR(lo)->i + ofs >= 0
that the result (constant) integer value for this IR is not negative and we don't
lose its sign and can use the cheaper instruction.

> Although, I’m trying to get into Mike’s business again. So it LGTM as a backport.
> 
> Regards,
> Sergos
> 
> 

<snipped>

> > -- 
> > Best regards,
> > Sergey Kaplun
> 

-- 
Best regards,
Sergey Kaplun

  reply	other threads:[~2021-10-29  7:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 18:53 Sergey Kaplun via Tarantool-patches
2021-10-27 16:08 ` sergos via Tarantool-patches
2021-10-28 11:36   ` Sergey Kaplun via Tarantool-patches
2021-10-28 12:37     ` sergos via Tarantool-patches
2021-10-29  7:49       ` Sergey Kaplun via Tarantool-patches [this message]
2022-06-28 13:21 ` Igor Munkin via Tarantool-patches
2022-06-30 12:09 ` Igor Munkin via Tarantool-patches

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YXune+a3cnrGFQat@root \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=sergos@tarantool.org \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH luajit] Fix FOLD rule for strength reduction of widening.' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox