public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: gcc-patches@gcc.gnu.org
Cc: Eric Botcazou <ebotcazou@adacore.com>,
	Ian Lance Taylor <iant@google.com>,
	       Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
	       Arnaud Charlet <charlet@adacore.com>,
	       "Joseph S. Myers" <joseph@codesourcery.com>,
	       Gerald Pfeifer <gerald@pfeifer.com>
	java-patches@gcc.gnu.org,        libstd++@gcc.gnu.org
Subject: Re: Provide 64-bit default Solaris/x86 configuration (PR target/39150)
Date: Thu, 07 Jul 2011 10:04:00 -0000	[thread overview]
Message-ID: <ydd1uy2h0lw.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <yddvcvfk5gm.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's	message of "Wed, 06 Jul 2011 13:34:49 +0200")

Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:

> There has long been some clamoring for a amd64-*-solaris2 configuration
> similar to sparcv9-sun-solaris2.  I've resisted this for quite some
> time, primarily because it doubles the maintenance effort of testing
> both the 32-bit default and 64-bit default configurations.
[...]
> I think practically the whole patch falls under the Solaris
> maintainership, with the possible exception of the change to the copy of
> libtool.m4 in libgo/config.  This is not for the technical content, but
> for the special commit rules to that directory.  Ian?
>  
> Anyway, this part of the patch will have to go to upstream libtool.
> Ralf, could you take care of that?
>
> Bootstrapped without regression on i386-pc-solaris2.10 (both 32-bit
> default and 64-bit default configurations), i386-pc-solaris2.11 and
> sparc-sun-solaris2.11 in progress.
[...]
> Once all the bootstraps have finished, I'll commit this patch (at least
> the non-libgo parts) unless anything unexpected comes up.

All bootstraps have completed without regressions, so I've installed the
patch as is, after verifying that the libgo parts aren't present in the
upstream Go repo.

I've also synced the toplevel configure.ac/configure changes to src.

One other issue: it was suggested that the 64-bit compiler might
actually be faster than a 32-bit one.  At least bootstrap times speak
another language: on a Sun Fire X4450 running Solaris 10 with 4 x 2.93
GHz Quad-Core Xeon Xeon X7350, I find for make -j32 + make -j32 -k check
for both multilibs:

      		64-bit		32-bit

		as/ld

      real     	1:59:28.66	1:52:15.55
      user     	7:14:33.93	6:43:25.84
      sys      	5:26:30.66	4:41:02.78

      		gas/ld

		2:02:47.64	1:54:24.51
		7:10:41.93	6:39:39.39
		5:37:15.86	4:51:41.02

		gas/gld

		1:59:57.13	1:45:13.18
		7:57:37.13	7:11:41.83
		5:11:58.14	4:04:26.97

Same picture on a Sun Fire X4600 M2 running Solaris 11 with 8 x 2.6 GHz
Dual-Core Opteron 8218.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  parent reply	other threads:[~2011-07-07 10:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 11:51 Rainer Orth
2011-07-06 15:34 ` Eric Botcazou
2011-07-06 15:57   ` Rainer Orth
2011-07-06 16:23     ` Eric Botcazou
2011-07-07 10:04 ` Rainer Orth [this message]
2011-07-07 19:14   ` Ian Lance Taylor
2011-07-08 12:39     ` Rainer Orth
2011-07-08 14:35       ` Ian Lance Taylor
2011-07-08 15:49         ` Rainer Orth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ydd1uy2h0lw.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=charlet@adacore.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=iant@google.com \
    --cc=joseph@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).