Oops, sorry, there is issues in fact with the new LLVM backend ! (NB:
I made a mistake by compiling/running the fastcomp version of D3, and
not the LLVM version).
So the error happens at link stage, with the following output:
error: undefined symbol: g$SIMDProcessor
error: undefined symbol: g$_ZN11idHashIndex13INVALID_INDEXE
error: undefined symbol: g$_ZN5idLib10cvarSystemE
error: undefined symbol: g$_ZN5idLib10fileSystemE
error: undefined symbol: g$_ZN5idLib3sysE
error: undefined symbol: g$_ZN5idLib6commonE
error: undefined symbol: g$_ZN6idCVar10staticVarsE
error: undefined symbol: g$_ZN6idMatX7tempPtrE
error: undefined symbol: g$_ZN6idMath10SQRT_THREEE
error: undefined symbol: g$_ZN6idMath11FLT_EPSILONE
error: undefined symbol: g$_ZN6idMath11SQRT_1OVER2E
error: undefined symbol: g$_ZN6idMath12ONEFOURTH_PIE
error: undefined symbol: g$_ZN6idMath2PIE
error: undefined symbol: g$_ZN6idMath5iSqrtE
error: undefined symbol: g$_ZN6idMath6TWO_PIE
error: undefined symbol: g$_ZN6idMath7HALF_PIE
error: undefined symbol: g$_ZN6idMath8INFINITYE
error: undefined symbol: g$_ZN6idMath9M_DEG2RADE
error: undefined symbol: g$_ZN6idMath9M_RAD2DEGE
error: undefined symbol: g$_ZN6idVecX7tempPtrE
error: undefined symbol: g$_ZN6idVecX9tempIndexE
error: undefined symbol: g$_ZTV14idSIMD_Generic
error: undefined symbol: g$common
error: undefined symbol: g$cvarSystem
error: undefined symbol: g$mat3_identity
error: undefined symbol: g$vec3_origin
error: undefined symbol: __memory_base
error: undefined symbol: __table_base
Most of the undefined symbols are global variables or constants in D3
code. I am not sure what is the root cause of the problem.
However, "__table_base" and "__memory_base" undefined symbols looks
quite suspect in my opinion. Any hints about where to look ?
Le 05/06/2019 à 23:34, Gabriel Cuvillier a écrit :
Ok, good to know about the upcoming LLVM backend !
I did a few tests of that new backend with the Doom 3 port. Except for
EMTEPRETER which is not supported (oops, too bad. I can no more yield
to the browser during the long loading screens!), everything else run
fine.
I did not noticed significant runtime performance improvement though,
but I guess it is because the real bottleneck in D3wasm lies in the
GL=>WebGL glue code (or somewhere else, but not in the "pure" wasm
binary).
It look like the compilation/link is faster, but maybe that's me.
Le 05/06/2019 à 23:15, Alon Zakai a écrit :
In general, you can just do
emsdk install 1.38.34
(or emsdk install latest gets the latest version). That installs
it with fastcomp, the current default backend. If you do
emsdk install 1.38.34-upstream
Then it gets the LLVM upstream wasm backend instead. We'll be
switching to it by default soon, and will have a larger announcement.
Basically we want to stabilize the migration to the new CI first.
- Alon
On Wed, Jun 5, 2019 at 2:11 PM Gabriel Cuvillier
<gabriel.cuvill...@gmail.com <mailto:gabriel.cuvill...@gmail.com>> wrote:
Note that I am not sure if we have to use
sdk-releases-upstream-<the_unique_identifier>-64bit
or
sdk-releases-fastcomp-<the_unique_identifier>-64bit
I don't get exactly what is the difference between the two
Le 05/06/2019 à 23:09, Patrik Weiskircher a écrit :
Ah, that'll already solve my problem. Doesn't have to be pretty,
just want to be able to specify a specific version. Thank you so
much!
On Wednesday, June 5, 2019 at 4:50:55 PM UTC-4, Gabriel CV wrote:
It look like things have changed a bit recently.
Actually, you can know the unique identifier of the last
precompiled SDK available in the file
"emscripten-releases-tags.txt" file (after issuing "emsdk
update-tags" commands)
On my side the contents is:
{
"latest": "1.38.33",
"releases": {
"1.38.33": "3b8cff670e9233a6623563add831647e8689a86b"
// this is the unique identifier
}
}
Then with that info I can do:
./emsdk install
sdk-releases-upstream-<the_unique_identifier>-64bit
This will install the 1.38.33. This is not very convenient I
think, but it works
Gabriel
Le 05/06/2019 à 21:59, Patrik Weiskircher a écrit :
Hey Alon!
I have a question. We currently have our CI setup to
compile specific versions that we define (currently we're
running on `1.38.31`) using `emsdk install
sdk-tag-${VERSION}-64bit`. We're currently running into a
little problem after updating one of our dependencies and I
figured I should just simply try out the latest version and
hope it'll work. But it doesn't seem like we can do a
`emsdk install sdk-tag-1.38.33-64bit` anymore - it says the
version doesn't exist.
Is this intended like this and from now on only `latest` is
supported? This would be a little problematic for us as we
really would like to pin down our versions (we previously
had trouble with new versions introducing new bugs).
Thanks for all your work, we all at PSPDFKit really
appreciate it :)
Patrik
On Wednesday, May 29, 2019 at 1:45:45 PM UTC-4, Alon Zakai
wrote:
If you get emsdk master, and do
emsdk install latest
emsdk activate latest
then it will install 1.38.33 (or later, if there is one
by the time you read this) from the new
emscripten-releases build infrastructure. We've done
some early testing recently as mentioned here:
https://groups.google.com/d/msg/emscripten-discuss/WhDtqVyW_Ak/8DfDnfk0BgAJ
After fixing some issues, there seem to be no
showstoppers, so this is us moving to the next stage in
the transition from the old builders to the new ones.
(If all goes well then the stage after this will be to
remove those old builders.)
Please report any issues you see!
Known issue: "no version information" warning on some
linux machines,
https://github.com/emscripten-core/emscripten/issues/8697,
that we need to figure out.
- Alon
--
You received this message because you are subscribed to the
Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to
emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/emscripten-discuss/04241de6-3244-4c6f-b9ce-064d790815c6%40googlegroups.com
<https://groups.google.com/d/msgid/emscripten-discuss/04241de6-3244-4c6f-b9ce-064d790815c6%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the
Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to
emscripten-discuss+unsubscr...@googlegroups.com
<mailto:emscripten-discuss+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/emscripten-discuss/45a0a10c-35ce-4ac8-bb3f-8e9627bf0390%40googlegroups.com
<https://groups.google.com/d/msgid/emscripten-discuss/45a0a10c-35ce-4ac8-bb3f-8e9627bf0390%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the
Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to emscripten-discuss+unsubscr...@googlegroups.com
<mailto:emscripten-discuss+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/emscripten-discuss/48a943aa-9768-6337-aa9a-1e22f3262265%40gmail.com
<https://groups.google.com/d/msgid/emscripten-discuss/48a943aa-9768-6337-aa9a-1e22f3262265%40gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to emscripten-discuss+unsubscr...@googlegroups.com
<mailto:emscripten-discuss+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/emscripten-discuss/CAEX4NpRnyqZn7jjmTY2aPZNcYqpb3fSSomtGdRUO6vc-rj2Hgw%40mail.gmail.com
<https://groups.google.com/d/msgid/emscripten-discuss/CAEX4NpRnyqZn7jjmTY2aPZNcYqpb3fSSomtGdRUO6vc-rj2Hgw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/emscripten-discuss/652ae7a5-4405-2d77-2ceb-a5d208a9dd33%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
