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: <1436476001.24803.165.camel@surprise> (raw)
In-Reply-To: <CACXZuxdP=W1dmW_=xoY2u60Wafku_oOtBfLPZP+rub2N_qrLhQ@mail.gmail.com>
On Thu, 2015-07-09 at 21:52 +0100, Dibyendu Majumdar wrote:
> On 9 July 2015 at 20:22, David Malcolm <dmalcolm@redhat.com> wrote:
> >> but it does seem to have caused
> >> the optimization bug to go away - i.e. the tests now pass. I will run
> >> more tests tomorrow to see if this is true under all optimization
> >> settings.
> >
> > FWIW, I suspect that this is effectively just papering over the problem,
> > and that it will come back to bite us, just with a more complicated
> > reproducer :(
> >
>
> Yes agree.
>
> > Does something like:
>
> >
> >
> > function x(some_arg)
> > local IX
> > if ((some_arg or true) and false) then
> > IX = true
> > end;
> > return ((some_arg or true) and false)
> > end
> > assert(x() == false)
> >
> >
> >
> > exhibit the bug? (have never programmed Lua, so this probably even
> > isn't syntactically correct, but hopefully you get the idea, with
> > const-propagation of 10's value and typecode lots of code gets optimized
> > away, so using an arg of unknown type to thwart that and hopefully get
> > the bug to re-manifest itself).
> >
>
> Actually that is valid Lua. Since you aren't passing a value to x()
> then some_arg will be NIL. In Lua, NIL and false are false, everything
> else is true.
> The example above works okay as is, and also when I pass 10 to x().
> As usual with certain bugs - only a specific set of circumstances trigger it.
>
> >
> > (Note that I've managed to isolate a minimal reproducer for the problem,
> > as noted in another mail this thread)
> >
>
> Yes that is very good news. Hope you will soon discover the root cause.
Root cause found: it turns out that part of GCC's alias analysis is
deferred to a frontend-specific hook:
LANG_HOOKS_GET_ALIAS_SET
For C/C++/Objective C this hook allows type-punning when directly
accessing unions, and the Ravi code assumes this.
I hadn't implemented this hook for libgccjit, so the optimizer assumes
that in this sequence of assignments:
(1) R1.value_.b = 0;
(2) R1.value_.i = CONST0.value_.i;
(3) R1.value_.b = 0;
that (1) and (3) have the same LHS, but (2) has a different LHS.
Hence it assumes that (3) is redundant, due to (1), and optimizes it
away.
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66812 for more gory
details.
The fix will be to implement the LANG_HOOKS_GET_ALIAS_SET internal GCC
API thus giving libgccjit some rules about aliasing. Some options:
(i) make it identical to C.
(ii) give the client code some control over this
My initial gut feeling is to go with (i).
next prev parent reply other threads:[~2015-07-09 21:14 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 ` Filed PR jit/66812 for the " 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 ` 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
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 ` 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 ` A possible " 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 ` 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/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
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=1436476001.24803.165.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).