On 08/30/2017 03:22 PM, Magnus Ihse Bursie wrote:
I'm sure it's *possible*. I'm also fairly certain it will be messy. :)
I already guess that.
Unfortunately, the usage of various defines in presence of zero seems not very well defined. That is, should SPARC be defined alongside ZERO, or should it not be defined when ZERO is defined, if building zero on sparc.
As far as I know, VAR_CPU is always defined, independent of the build type.
The current effect, if I remember correctly, is that both ZERO and SPARC are defined if building zero on sparc, but only SPARC if building a "normal" sparc build.
That's what I observed as well.
There is also a ZERO_LIBARCH, but I fail to understand the purpose of this.
I see.
But your problem seems to be that the file itself is not included. I'm not sure how the hotspot include logic determines which platform specific files to include. Possibly they have a "and !definied(ZERO)" in the logic.
It's actually a .cpp file as you mentioned in your second mail. I was already pondering converting the file to a header file and then including it. However, the specific path where the SPARC-version of memset is located is not accessible on Zero due to a missing -I directive. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
