sparc-sun-solaris versus sparc64-sun-solaris

sparc-sun-solaris versus sparc64-sun-solaris

[Gerald Pfeifer]

config.guess currently detects _any_ SPARC host running Solaris as
sparc-sun-solaris, even if it is capable of and in fact running in
64-bit mode.

FreeBSD, GNU/Linux,... OTH are config.guessed as sparc64-..., so I wonder
whether the following patch (or a variant thereof) would be appropriate?

Gerald

2003-06-19  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>

	* config.guess: Properly detect Solaris 2.x running a 64-bit kernel.

Index: config.guess
===================================================================
RCS file: /cvs/gcc/gcc/config.guess,v
retrieving revision 1.61
diff -u -3 -p -r1.61 config.guess
--- config.guess	14 Jun 2003 14:08:09 -0000	1.61
+++ config.guess	19 Jun 2003 20:32:56 -0000
@@ -335,7 +335,11 @@ case "${UNAME_MACHINE}:${UNAME_SYSTEM}:$
 	echo sparc-hal-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
 	exit 0 ;;
     sun4*:SunOS:5.*:* | tadpole*:SunOS:5.*:*)
-	echo sparc-sun-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
+	case `isainfo` in
+	    *sparcv9*) MODE="64" ;;
+	    *) MODE="" ;;
+	esac
+	echo sparc${MODE}-sun-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
 	exit 0 ;;
     i86pc:SunOS:5.*:*)
 	echo i386-pc-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`

Re: sparc-sun-solaris versus sparc64-sun-solaris

[Jeff Sturm]

On Thu, 19 Jun 2003, Gerald Pfeifer wrote:
>      sun4*:SunOS:5.*:* | tadpole*:SunOS:5.*:*)
> -	echo sparc-sun-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
> +	case `isainfo` in
> +	    *sparcv9*) MODE="64" ;;
> +	    *) MODE="" ;;
> +	esac
> +	echo sparc${MODE}-sun-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`

Traditionally, Solaris users always get a compiler that creates 32-bit
executables, unless they compile with -m64 or configure as sparc64-*-*.

Changing that default would likely be very surprising to those users.  Is
it worth doing?

Jeff

Re: sparc-sun-solaris versus sparc64-sun-solaris

[Joe Buck]

On Thu, Jun 19, 2003 at 05:39:22PM -0400, Jeff Sturm wrote:
> On Thu, 19 Jun 2003, Gerald Pfeifer wrote:
> >      sun4*:SunOS:5.*:* | tadpole*:SunOS:5.*:*)
> > -	echo sparc-sun-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
> > +	case `isainfo` in
> > +	    *sparcv9*) MODE="64" ;;
> > +	    *) MODE="" ;;
> > +	esac
> > +	echo sparc${MODE}-sun-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
> 
> Traditionally, Solaris users always get a compiler that creates 32-bit
> executables, unless they compile with -m64 or configure as sparc64-*-*.
> 
> Changing that default would likely be very surprising to those users.  Is
> it worth doing?

In my view, the default should not be changed: as it is, we build a
compiler that can generate either 32-bit or 64-bit code (with -m64
switch).

Re: sparc-sun-solaris versus sparc64-sun-solaris

[Mark Mitchell]

On Thu, 2003-06-19 at 14:39, Jeff Sturm wrote:
> On Thu, 19 Jun 2003, Gerald Pfeifer wrote:
> >      sun4*:SunOS:5.*:* | tadpole*:SunOS:5.*:*)
> > -	echo sparc-sun-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
> > +	case `isainfo` in
> > +	    *sparcv9*) MODE="64" ;;
> > +	    *) MODE="" ;;
> > +	esac
> > +	echo sparc${MODE}-sun-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
> 
> Traditionally, Solaris users always get a compiler that creates 32-bit
> executables, unless they compile with -m64 or configure as sparc64-*-*.

How exactly is one supposed to "configure as sparc64-*-*"?

I tried "--target=sparc64-sun-solaris2.9" and it tried to build a cross
compiler; it didn't want to use ordinary "as" and so forth.

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

Re: sparc-sun-solaris versus sparc64-sun-solaris

[Jeff Sturm]

On 19 Jun 2003, Mark Mitchell wrote:
> How exactly is one supposed to "configure as sparc64-*-*"?

--host=sparc64-sun-solaris2.9

Jeff

Re: sparc-sun-solaris versus sparc64-sun-solaris

[Mark Mitchell]

On Thu, 2003-06-19 at 14:58, Jeff Sturm wrote:
> On 19 Jun 2003, Mark Mitchell wrote:
> > How exactly is one supposed to "configure as sparc64-*-*"?
> 
> --host=sparc64-sun-solaris2.9

That's a bit non-intuitive to me, but that's OK.

Thanks,

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

Re: sparc-sun-solaris versus sparc64-sun-solaris

[Alexandre Oliva]

On Jun 19, 2003, Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> wrote:

> FreeBSD, GNU/Linux,... OTH are config.guessed as sparc64-..., so I wonder
> whether the following patch (or a variant thereof) would be appropriate?

FWIW, I've always disliked that, even if I configure with a CC that
generates 32-bit by default, config.guess would still detect
sparc64-unknown-linux-gnu.  IMHO, changing this for Solaris too would
just propagate the pain to Solaris users too.  I'd much rather have
config.guess actually run the compiler to tell whether to guess sparc
or sparc64.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

Re: sparc-sun-solaris versus sparc64-sun-solaris

[Eric Botcazou]

> In my view, the default should not be changed: as it is, we build a
> compiler that can generate either 32-bit or 64-bit code (with -m64
> switch).

Note that a compiler configured as sparc64-sun-solaris does satisfy this 
constraint too: you can use -m32 to generate 32-bit code.

-- 
Eric Botcazou

Re: sparc-sun-solaris versus sparc64-sun-solaris

[Eric Botcazou]

> Changing that default would likely be very surprising to those users.  Is
> it worth doing?

I don't think so:
- the Sun compiler produces 32-bit code by default,
- building sparc64-sun-solaris from the Sun compiler requires the user to 
pass a cryptic CC variable to the configure script. Sure this is documented, 
but I'd rather avoid any gratuitous pitfall,
- in my experience, the 64-bit compiler is slower than the 32-bit one on the 
same machine (Ultra-60).

-- 
Eric Botcazou