Re: why no -xcode=picxx and -xmemalign flags on X86?

Henry Townsend <henry.townsend@xxxxxxxx> writes:

Now we get to the point. Of course the two compilers are going to emit
different output; the question is why what is nominally the *same
compiler* not be flag-for-flag compatible between Sparc and x86? I
expect to deal with differences like -fpic for GCC and -Kpic for Sun
Studio. I don't expect to have to "port" compiler flags between Sun
Studio on two different architectures.

That's because the instruction sets dictate different addressing
modes; -Kpic/-kpic was not expressive enough for SPARC code generation
but still is for IA32/64.

(the pic13 and pic32 codes suggest bit widths which are specific to
an architecture)

This is a big deal here - I'm maintaining a build system for a very
large product (one for which, ironically, Sun is a major customer). I
already have to deal with differences in the native compilers on HP,
AIX, Linux, etc. But this is beyond the pale. How can they be on the
11.0 major release of a major suite and not have spent a few days
syncing up the flags between their two major platforms is beyond me.

You already have to have build differences for SPARC and x86, or
not?

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
.