>> So one could consider CHPL_TARGET_PLATFORM something like a noun and
>> CHPL_RT_ARCH something like an adjective?
>
> They are actually a bit more orthogonal than that. CHPL_TARGET_PLATFORM is
> more along the lines of what operating system you are using, while
> CHPL_RT_ARCH would be what processor you have in that machine.
I find myself wondering whether we should just make CHPL_TARGET_PLATFORM
more specific in cases where we want it to be more specific. I.e., should
we use 'linux64' as a means of saying "create a portable linux64 binary"
(what we do today) and 'core-avx2-linux64' as a means of saying "create a
linux64 binary that's customized to core-avx2?" We could either require
users to set these more stringent choices when they want better
performance (which seems safe, but a little too bad), or we could beef up
the chplenv/ scripts that auto-infer CHPL_*_PLATFORM to try to make them
auto-select a more focused target than they do today (which would be
challenging in the open-source cross-compilation environment... but
cross-compilation is tricky in the open-source case in general...).
Upside: Uses an existing environment variable? What else?
Downside: Would need to tease multiple pieces of information out of one
environment variable? What else?
If we were to create new variables, I think CHPL_TARGET_ARCH or
CHPL_TARGET_PROC is better than CHPL_RT_ARCH (and note that we could
support the equivalent CHPL_HOST_* setting for symmetry, if one wanted to
create a compiler that was potentially optimized to the host processor
architecture).
-Brad
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers
