From: David Malcolm <dmalcolm@redhat.com>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: jit@gcc.gnu.org
Subject: Re: Filed PR jit/66812 for the code generation issue
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <1436385256.24803.107.camel@surprise> (raw)
In-Reply-To: <CACXZuxcj_CRjOUy6TfexL9S9TmVRUB1Zpd9J8-Awj4ritUUbFA@mail.gmail.com>
On Wed, 2015-07-08 at 20:36 +0100, Dibyendu Majumdar wrote:
> On 8 July 2015 at 20:03, David Malcolm <dmalcolm@redhat.com> wrote:
> > On Wed, 2015-07-08 at 20:01 +0100, Dibyendu Majumdar wrote:
> >> On 8 July 2015 at 18:46, David Malcolm <dmalcolm@redhat.com> wrote:
> >> > Dibyendu: what Lua code generated the reproducer? What is the code
> >> > meant to be doing?
> >> >
> >>
> >> Hi Dave - the Lua test is this:
> >>
> >> function x()
> >> local IX
> >> if ((10 or true) and false) then
> >> IX = true
> >> end;
> >> return ((10 or true) and false)
> >> end
> >> assert(x() == false)
> >>
> >> In the original test IX is an upvalue - i.e. a variable in outer
> >> scope. This is my standalone version of the test. The original test is
> >> generated as part of the Lua test suite - its purpose is to test
> >> various permutations of boolean operators.
> >>
> >> The original test compares IX and the function return.
> >>
> >> The issue is that this test should return false - if you see the
> >> return statement. However when -O2 or -O3 is enabled it returns true.
> >>
> >> The if statement is indeed redundant in this cut down version as IX is
> >> a local variable. But the return statement is not redundant.
> >
> > Thanks. What does this look like as bytecodes?
> >
>
> Ok the bug is still there - I was running the test incorrectly. I have
> attached the standalone replication and the output.
> Note that if I remove the redundant if statement then it works correctly.
Thanks.
BTW, are Lua/Ravi constants truly constant? If so, then I'd believe
you'd get a performance win by implementing LOADK by emitting code to
write the specific tt and value_ directly, rather than code that copies
a value from the table.
This would enable the optimizer to "know" the tt and value_, and
optimize accordingly. For example, in this case, I believe it would
allow the function to be optimized away down to the equivalent of just a
"return false;". Obviously won't help much for a function without a
loop, but if it saves instructions inside a loop, that's probably a win.
(...though maybe not before we track down this issue)
next prev parent reply other threads:[~2015-07-08 20:02 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 A possible " Dibyendu Majumdar
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Filed PR jit/66811: jit jumps aren't compilable as C (Re: A possible code generation issue) David Malcolm
2015-01-01 0:00 ` Filed PR jit/66811: jit dumps " David Malcolm
2015-01-01 0:00 ` A possible code generation issue Dibyendu Majumdar
2015-01-01 0:00 ` PR jit/66783 (Re: A possible code generation issue) David Malcolm
2015-01-01 0:00 ` [PATCH, committed] PR jit/66783: prevent use of opaque structs David Malcolm
2015-01-01 0:00 ` Filed PR jit/66812 for the code generation issue David Malcolm
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm [this message]
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` [PATCH] PR jit/66812: Candidate fix for for the code generation issue, v1 David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Filed PR jit/66812 for the code generation issue Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm
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=1436385256.24803.107.camel@surprise \
--to=dmalcolm@redhat.com \
--cc=jit@gcc.gnu.org \
--cc=mobile@majumdar.org.uk \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).