On Fri, Dec 16, 2022 at 1:21 AM Gregory Propf wrote:
> I just checked with version 3.1.28 and there's no 'this' pointer there
> either. I also tried 3.1.25 and it looks like 24 --> 25 is the point where
> the pointer died so to speak. So right now, 3.1.24 is the latest I can use.
> I'm using
I just checked with version 3.1.28 and there's no 'this' pointer there
either. I also tried 3.1.25 and it looks like 24 --> 25 is the point where
the pointer died so to speak. So right now, 3.1.24 is the latest I can use.
I'm using Ubuntu 22.04 on very recent Intel hardware.
On Thursday,
Hello Heejin, As far as a reproducer, you can clone my project
https://github.com/gpropf/clarity and do 'make showcase'. Set some
breakpoints around line 715 in the method setCppValFromJSVal() in the file
ClarityNode.hpp and then change some of the values in the text fields or
range controls on
I think this is likely to be an LLVM upstream problem than wasm-specific
problem. If you have a reproducer, that'd be helpful as well.
On Wed, Dec 7, 2022 at 1:02 PM Gregory Propf wrote:
> Interesting. I didn't know about git bisect before so this is a good tool
> to have. I mainly just wanted
Interesting. I didn't know about git bisect before so this is a good tool
to have. I mainly just wanted to let the devs and users know this was
happening. Like I said for now I can just use 3.1.24. It won't be a problem
unless it turns out I can never upgrade beyond that. Unfortunately I don't
Bisection might be useful here, as in theory any LLVM change could cause
such a difference or a bug. It's pretty simple to bisect using the emsdk:
https://emscripten.org/docs/contributing/developers_guide.html#bisecting
On Tue, Dec 6, 2022 at 4:22 PM Gregory Propf wrote:
> I just noticed
I just noticed something while debugging a program. A few days ago I
migrated from 3.1.24 to 3.1.26. It now seems that, in Chrome at least, I
only see the literal value of the 'this' pointer but can't see the
components of the object. My CFLAGS are still the same: -O0 -g -std=c++17.
For now