From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: David Malcolm <dmalcolm@redhat.com>
Cc: jit@gcc.gnu.org
Subject: Re: Weird problem
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <CACXZuxcV94XUPS9=N6KNLj-DbAjCKeJQYi+jQ2v6jfEgQmxMfA@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxeqNTjyyikrTuAWvJdQ1PtYc8rdXDYdD2Ywsh=TxJgaVw@mail.gmail.com>
On 29 June 2015 at 22:25, Dibyendu Majumdar <mobile@majumdar.org.uk> wrote:
> On 29 June 2015 at 22:08, David Malcolm <dmalcolm@redhat.com> wrote:
>> Does it help if you introduce an intermediate to hold the result of the
>> call to luaV_tonumber_ before comparing it against zero? It
>> *shouldn't*, but maybe we have a libgccjit bug.
>>
Tried this - did not help. The print I put in shows that the address
that luaV_number() is getting is not the same.
number 0x7ffce864f5e0 = 0.000000 before call to luaV_number
set *0x7ffce864f5e8 to 6.200000
number ok = 0.000000
And yet it is the address of the same variable being passed.
I cannot see what I am doing wrong - perhaps you can spot in the
reproducer dump.
Thanks and Regards
Dibyendu
next prev parent reply other threads:[~2015-06-29 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-01 0:00 Dibyendu Majumdar
2015-01-01 0:00 ` 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='CACXZuxcV94XUPS9=N6KNLj-DbAjCKeJQYi+jQ2v6jfEgQmxMfA@mail.gmail.com' \
--to=mobile@majumdar.org.uk \
--cc=dmalcolm@redhat.com \
--cc=jit@gcc.gnu.org \
/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).