1056 2014-08-30 05:13:14 +0200 Wrong guess on the endianness of powerpc 2019-03-29 17:54:46 +0100 1 1 3 JogAmp Gluegen core 2.3.0 pc_ppc all RESOLVED FIXED --- enhancement --- 1126 0 tmancill sgothel --- --- oldest_to_newest 4134 0 627 tmancill 2014-08-30 05:13:14 +0200 Created attachment 627 scilab stacktrace on ppc Hi - in looking at the source code, it it doesn't appear that powerpc is detected as little endian x86. Attached is an example stack trace. 4368 1 sgothel 2014-10-09 07:41:08 +0200 The static configuration makes a wrong 'guess' here and comparison w/ dynamic probing fails. I assume the dynamic config to reflect the true values, otherwise our probing is false. We probe variable type size and alignment, as well as other values using native code from our native library. Some values are probed via Java. The static value probably is at fault here. Incompatible fields: static: dynamic: littleEndian true false int64* 8 / 4 8 / 8 double* 8 / 4 8 / 8 ldouble* 12 / 4 16 / 16 (*) size/alignment It could help if you send the whole log up until this failure w/ all debug flags enabled! Further, please add OS and CPU information. If you are knowledgeable about CPU cpu configurations, maybe you can help picking the proper static configuration: MachineDescriptionRuntime.getStatic(). The usage of static values is indeed a huge issue here. The static version is used in generated structs for length - and the offset is generated at compile time using the alignment and the size. We might could move the table generation to runtime, which would allow us to drop the static config. However, this would require us to rewrite package 'jogamp.common.os.elf', which also uses structs from the ELF headers .. which in turn determines which native library we load. Full cycle: The latter also contains code for probing the dynamic values. In short: Getting rid of static config will be some work. 4571 2 sgothel 2015-02-02 00:32:10 +0100 'Should' be fixed by changes for Bug 1126. In case this (or a related) issue still persists, please reopen this bug and comment. Note: I don't have PPC hardware here. 4576 3 tmancill 2015-02-04 05:33:16 +0100 (In reply to comment #2) > 'Should' be fixed by changes for Bug 1126. > > In case this (or a related) issue still persists, > please reopen this bug and comment. > > Note: I don't have PPC hardware here. Thanks! I'll test it and follow-up. 627 2014-08-30 05:13:14 +0200 2014-08-30 05:13:14 +0200 scilab stacktrace on ppc scilab_powerpc_stacktrace.txt text/plain 710 tmancill CkNhdXNlZCBieTogamF2YS5sYW5nLlJ1bnRpbWVFeGNlcHRpb246IEluY29tcGF0aWJsZSBNYWNo aW5lRGVzY3JpcHRpb25zOgogU3RhdGljIE1hY2hpbmVEZXNjcmlwdGlvblN0YXRpYzogWDg2XzMy X1VOSVgoMSk6IE1hY2hpbmVEZXNjcmlwdGlvbjogcnVudGltZVZhbGlkYXRlZCBmYWxzZSwgbGl0 dGxlRW5kaWFuIHRydWUsIDMyQml0IHRydWUsIHByaW1pdGl2ZSBzaXplIC8gYWxpZ25tZW50Ogog IGludDggMSAvIDEsIGludDE2IDIgLyAyCiAgaW50IDQgLyA0LCBsb25nIDQgLyA0CiAgaW50MzIg NCAvIDQsIGludDY0IDggLyA0CiAgZmxvYXQgNCAvIDQsIGRvdWJsZSA4IC8gNCwgbGRvdWJsZSAx MiAvIDQKICBwb2ludGVyIDQgLyA0LCBwYWdlIDQwOTYKIFJ1bnRpbWUgTWFjaGluZURlc2NyaXB0 aW9uOiBydW50aW1lVmFsaWRhdGVkIHRydWUsIGxpdHRsZUVuZGlhbiBmYWxzZSwgMzJCaXQgdHJ1 ZSwgcHJpbWl0aXZlIHNpemUgLyBhbGlnbm1lbnQ6CiAgaW50OCAxIC8gMSwgaW50MTYgMiAvIDIK ICBpbnQgNCAvIDQsIGxvbmcgNCAvIDQKICBpbnQzMiA0IC8gNCwgaW50NjQgOCAvIDgKICBmbG9h dCA0IC8gNCwgZG91YmxlIDggLyA4LCBsZG91YmxlIDE2IC8gMTYKICBwb2ludGVyIDQgLyA0LCBw YWdlIDQwOTYKIGF0IGNvbS5qb2dhbXAuY29tbW9uLm9zLlBsYXRmb3JtLjxjbGluaXQ+KFBsYXRm b3JtLmphdmE6MjI3KQogLi4uIDQgbW9yZQo=