Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Dennis Clarke]

> Dennis Clarke <dclarke@blastwave.org> writes:
>
>>> GCC 4.7.0 Release Candidate available from gcc.gnu.org
>>>
>>> The first release candidate for GCC 4.7.0 is available from
>>>
>>>  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>>>
>>> and shortly its mirrors.  It has been generated from SVN revision 184777.
>>>
>>> I have so far bootstrapped and tested the release candidate on
>>> x86_64-linux.  Please test it and report any issues to bugzilla.
>>>
>>> If all goes well, I'd like to release 4.7.0 in about three weeks.
>>
>> I'll drop it on Solaris. Give it a push. Do we realy really need that
>> ppl/cloog stuff? I have never seen it build and pass any tests, ever,
>> even once, on Solaris with or without Sun Studio compilers or GCC or
>> prayer and geek magic under a full moon.  Seriously.
>
> Given that PPL is a C++ library, you need to build it with g++ since
> Studio CC and g++ aren't ABI-compatible.
>
> That said, I'm using them in my Solaris GCC bootstraps, although it
> admittedly took some effort to build initially and using it requires you
> to jump through hoops to get the configure options right.  I agree that
> this is an incredible mess right now.
>
>> So really, it that stuff a "need" or a "nice to have" ?
>
> install.texi documents them as optional:
>
> Necessary to build GCC with the Graphite loop optimizations.
>
> but that sentence could probably be clarified.
>
> 	Rainer

Well this topic is in play for me right now and I'd love your input
also.

I just finished a prep for bootstrapping gcc 4.6.3 and 4.7.0-RC1 on
Solaris 8 sparc and i386 here. One of the initial steps is to ensure
we have gmp/mpfr/mpc flawless which I do :


.
.
.
PASS: tsub_ui
PASS: ttan
PASS: ttanh
PASS: tui_div
PASS: tui_ui_sub
GMP: include 5.0.4, lib 5.0.4
MPFR: include 3.1.0, lib 3.1.0
MPC: include 0.9, lib 0.9
PASS: tget_version
===================
All 60 tests passed
===================
gmake[2]: Leaving directory `/opt/bw/src/mpc-0.9-SunOS5.8-i386.001/tests'
gmake[1]: Leaving directory `/opt/bw/src/mpc-0.9-SunOS5.8-i386.001/tests'
Making check in doc
gmake[1]: Entering directory `/opt/bw/src/mpc-0.9-SunOS5.8-i386.001/doc'
gmake[1]: Nothing to be done for `check'.
gmake[1]: Leaving directory `/opt/bw/src/mpc-0.9-SunOS5.8-i386.001/doc'
gmake[1]: Entering directory `/opt/bw/src/mpc-0.9-SunOS5.8-i386.001'
gmake[1]: Leaving directory `/opt/bw/src/mpc-0.9-SunOS5.8-i386.001'
$
$ uname -a
SunOS titan 5.8 Generic_127722-03 i86pc i386 i86pc
$ cat /etc/release
                       Solaris 8 2/02 s28x_u7wos_08a INTEL
           Copyright 2002 Sun Microsystems, Inc.  All Rights Reserved.
                           Assembled 18 December 2001
$ psrinfo -v
Status of virtual processor 0 as of: 03/02/12 20:25:50
  on-line since 04/28/11 17:39:44.
  The i386 processor operates at 400 MHz,
        and has an i387 compatible floating point processor.
Status of virtual processor 1 as of: 03/02/12 20:25:50
  on-line since 04/28/11 17:39:48.
  The i386 processor operates at 400 MHz,
        and has an i387 compatible floating point processor.
$

So I have had no issues with old Solaris 8 and Sparc32 or Sparc 64-bit
regardless if it is Sparc64 Fujitsu, Niagara T2 or old UltraSparc II.
I know I have to compile for x86_64 on Solaris 10. That is a given.

The question on my mind that requires ( or begs ) your input is should
I continue to trust the golden rule of the ABI and build, test and
release based on Solaris 8?  I don't really want to do the same
process over and over on Solaris 10 or 11 when I *know* that old
Solaris 8 is rock solid stable and the baseline ABI to be used.

Your thoughts ?

Dennis



-- 
--
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x1D936C72FA35B44B
+-------------------------+-----------------------------------+
| Dennis Clarke           | Solaris and Linux and Open Source |
| dclarke@blastwave.org   | Respect for open standards.       |
+-------------------------+-----------------------------------+

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[NightStrike]

On Mon, Mar 12, 2012 at 8:25 AM, Richard Guenther <rguenther@suse.de> wrote:
> On Mon, 12 Mar 2012, NightStrike wrote:
>
>> On Mon, Mar 12, 2012 at 5:59 AM, Richard Guenther <rguenther@suse.de> wrote:
>> > On Wed, 7 Mar 2012, NightStrike wrote:
>> >
>> >> On Fri, Mar 2, 2012 at 8:44 AM, Richard Guenther <rguenther@suse.de> wrote:
>> >> >
>> >> > GCC 4.7.0 Release Candidate available from gcc.gnu.org
>> >> >
>> >> > The first release candidate for GCC 4.7.0 is available from
>> >> >
>> >> >  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>> >> >
>> >> > and shortly its mirrors.  It has been generated from SVN revision 184777.
>> >> >
>> >> > I have so far bootstrapped and tested the release candidate on
>> >> > x86_64-linux.  Please test it and report any issues to bugzilla.
>> >> >
>> >> > If all goes well, I'd like to release 4.7.0 in about three weeks.
>> >>
>> >>
>> >> Building gmp/mpfr/mpc in tree fails in the configure-stage1-mpc step
>> >> with the current version of mpfr version 3.1.0, out since last
>> >> October, and mpc, version 0.9, out since Feb of 2011.  I'm guessing
>> >> the sources moved or something.
>> >>
>> >> For instance, just to get the configure step to pass, I had to change
>> >> the last line of the configure step in the generated Makefile from
>> >> this:
>> >>
>> >>           --disable-shared --with-gmp-include=$$r/$(HOST_SUBDIR)/gmp
>> >> --with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/.libs
>> >> --with-mpfr-include=$$s/mpfr
>> >> --with-mpfr-lib=$$r/$(HOST_SUBDIR)/mpfr/.libs
>> >>
>> >> to this:
>> >>
>> >>           --disable-shared --with-gmp-include=$$r/$(HOST_SUBDIR)/gmp
>> >> --with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/.libs
>> >> --with-mpfr-include=$$s/mpfr/src
>> >> --with-mpfr-lib=$$r/$(HOST_SUBDIR)/mpfr/.libs
>> >>
>> >>
>> >> The key section is adding /src on the end of --with-mpfr-include=$$s/mpfr/src
>> >>
>> >>
>> >> That gets the build further, but it still doesn't work.
>> >>
>> >> This same problem affects 4.6.
>> >
>> > The suggested versions of the packages in doc/install.texi are
>> > older than the ones you tried.
>> >
>> > Feel free to propose a patch for trunk, changing the recommended
>> > versions there.
>> >
>> > Richard.
>>
>> Ok.  But does that mean that to fix configure, we have to increase the
>> minimum version of mpfr?
>
> Well, or somehow support and detect both variants for in-tree builds.
> IMHO we should exactly allow a _single_ version of the libraries for
> in-tree builds (well, maybe allow patchlevel changes).  And we should
> document these versions as recommended.
>
> Richard.

There's already a patch for that on the bugzilla PR that went ignored.

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[NightStrike]

On Mon, Mar 12, 2012 at 8:05 AM, Dennis Clarke <dclarke@blastwave.org> wrote:
>
>> On Mon, Mar 12, 2012 at 5:59 AM, Richard Guenther <rguenther@suse.de> wrote:
>>> On Wed, 7 Mar 2012, NightStrike wrote:
>>>
>>>> On Fri, Mar 2, 2012 at 8:44 AM, Richard Guenther <rguenther@suse.de> wrote:
>>>> >
>>>> > GCC 4.7.0 Release Candidate available from gcc.gnu.org
>>>> >
>>>> > The first release candidate for GCC 4.7.0 is available from
>>>> >
>>>> >  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>>>> >
>>>> > and shortly its mirrors.  It has been generated from SVN revision 184777.
>>>> >
>>>> > I have so far bootstrapped and tested the release candidate on
>>>> > x86_64-linux.  Please test it and report any issues to bugzilla.
>>>> >
>>>> > If all goes well, I'd like to release 4.7.0 in about three weeks.
>>>>
>>>>
>>>> Building gmp/mpfr/mpc in tree fails in the configure-stage1-mpc step
>>>> with the current version of mpfr version 3.1.0, out since last
>>>> October, and mpc, version 0.9, out since Feb of 2011.  I'm guessing
>>>> the sources moved or something.
>>>>
>>>> For instance, just to get the configure step to pass, I had to change
>>>> the last line of the configure step in the generated Makefile from
>>>> this:
>>>>
>>>>           --disable-shared --with-gmp-include=$$r/$(HOST_SUBDIR)/gmp
>>>> --with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/.libs
>>>> --with-mpfr-include=$$s/mpfr
>>>> --with-mpfr-lib=$$r/$(HOST_SUBDIR)/mpfr/.libs
>>>>
>>>> to this:
>>>>
>>>>           --disable-shared --with-gmp-include=$$r/$(HOST_SUBDIR)/gmp
>>>> --with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/.libs
>>>> --with-mpfr-include=$$s/mpfr/src
>>>> --with-mpfr-lib=$$r/$(HOST_SUBDIR)/mpfr/.libs
>>>>
>>>>
>>>> The key section is adding /src on the end of
>>>> --with-mpfr-include=$$s/mpfr/src
>>>>
>>>>
>>>> That gets the build further, but it still doesn't work.
>>>>
>>>> This same problem affects 4.6.
>>>
>>> The suggested versions of the packages in doc/install.texi are
>>> older than the ones you tried.
>>>
>>> Feel free to propose a patch for trunk, changing the recommended
>>> versions there.
>>>
>>> Richard.
>>
>> Ok.  But does that mean that to fix configure, we have to increase the
>> minimum version of mpfr?
>
> seen no major problems thus far. Also, gmp,mpfr,mpc all build fine
> with all tests passed even on a very very old :

Are you building in tree?

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Richard Guenther]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2448 bytes --]

On Mon, 12 Mar 2012, NightStrike wrote:

> On Mon, Mar 12, 2012 at 5:59 AM, Richard Guenther <rguenther@suse.de> wrote:
> > On Wed, 7 Mar 2012, NightStrike wrote:
> >
> >> On Fri, Mar 2, 2012 at 8:44 AM, Richard Guenther <rguenther@suse.de> wrote:
> >> >
> >> > GCC 4.7.0 Release Candidate available from gcc.gnu.org
> >> >
> >> > The first release candidate for GCC 4.7.0 is available from
> >> >
> >> >  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
> >> >
> >> > and shortly its mirrors.  It has been generated from SVN revision 184777.
> >> >
> >> > I have so far bootstrapped and tested the release candidate on
> >> > x86_64-linux.  Please test it and report any issues to bugzilla.
> >> >
> >> > If all goes well, I'd like to release 4.7.0 in about three weeks.
> >>
> >>
> >> Building gmp/mpfr/mpc in tree fails in the configure-stage1-mpc step
> >> with the current version of mpfr version 3.1.0, out since last
> >> October, and mpc, version 0.9, out since Feb of 2011.  I'm guessing
> >> the sources moved or something.
> >>
> >> For instance, just to get the configure step to pass, I had to change
> >> the last line of the configure step in the generated Makefile from
> >> this:
> >>
> >>           --disable-shared --with-gmp-include=$$r/$(HOST_SUBDIR)/gmp
> >> --with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/.libs
> >> --with-mpfr-include=$$s/mpfr
> >> --with-mpfr-lib=$$r/$(HOST_SUBDIR)/mpfr/.libs
> >>
> >> to this:
> >>
> >>           --disable-shared --with-gmp-include=$$r/$(HOST_SUBDIR)/gmp
> >> --with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/.libs
> >> --with-mpfr-include=$$s/mpfr/src
> >> --with-mpfr-lib=$$r/$(HOST_SUBDIR)/mpfr/.libs
> >>
> >>
> >> The key section is adding /src on the end of --with-mpfr-include=$$s/mpfr/src
> >>
> >>
> >> That gets the build further, but it still doesn't work.
> >>
> >> This same problem affects 4.6.
> >
> > The suggested versions of the packages in doc/install.texi are
> > older than the ones you tried.
> >
> > Feel free to propose a patch for trunk, changing the recommended
> > versions there.
> >
> > Richard.
> 
> Ok.  But does that mean that to fix configure, we have to increase the
> minimum version of mpfr?

Well, or somehow support and detect both variants for in-tree builds.
IMHO we should exactly allow a _single_ version of the libraries for
in-tree builds (well, maybe allow patchlevel changes).  And we should
document these versions as recommended.

Richard.

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Dennis Clarke]

> On Mon, Mar 12, 2012 at 5:59 AM, Richard Guenther <rguenther@suse.de> wrote:
>> On Wed, 7 Mar 2012, NightStrike wrote:
>>
>>> On Fri, Mar 2, 2012 at 8:44 AM, Richard Guenther <rguenther@suse.de> wrote:
>>> >
>>> > GCC 4.7.0 Release Candidate available from gcc.gnu.org
>>> >
>>> > The first release candidate for GCC 4.7.0 is available from
>>> >
>>> >  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>>> >
>>> > and shortly its mirrors.  It has been generated from SVN revision 184777.
>>> >
>>> > I have so far bootstrapped and tested the release candidate on
>>> > x86_64-linux.  Please test it and report any issues to bugzilla.
>>> >
>>> > If all goes well, I'd like to release 4.7.0 in about three weeks.
>>>
>>>
>>> Building gmp/mpfr/mpc in tree fails in the configure-stage1-mpc step
>>> with the current version of mpfr version 3.1.0, out since last
>>> October, and mpc, version 0.9, out since Feb of 2011.  I'm guessing
>>> the sources moved or something.
>>>
>>> For instance, just to get the configure step to pass, I had to change
>>> the last line of the configure step in the generated Makefile from
>>> this:
>>>
>>>           --disable-shared --with-gmp-include=$$r/$(HOST_SUBDIR)/gmp
>>> --with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/.libs
>>> --with-mpfr-include=$$s/mpfr
>>> --with-mpfr-lib=$$r/$(HOST_SUBDIR)/mpfr/.libs
>>>
>>> to this:
>>>
>>>           --disable-shared --with-gmp-include=$$r/$(HOST_SUBDIR)/gmp
>>> --with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/.libs
>>> --with-mpfr-include=$$s/mpfr/src
>>> --with-mpfr-lib=$$r/$(HOST_SUBDIR)/mpfr/.libs
>>>
>>>
>>> The key section is adding /src on the end of
>>> --with-mpfr-include=$$s/mpfr/src
>>>
>>>
>>> That gets the build further, but it still doesn't work.
>>>
>>> This same problem affects 4.6.
>>
>> The suggested versions of the packages in doc/install.texi are
>> older than the ones you tried.
>>
>> Feel free to propose a patch for trunk, changing the recommended
>> versions there.
>>
>> Richard.
>
> Ok.  But does that mean that to fix configure, we have to increase the
> minimum version of mpfr?

I have tested builds of gmp/mpfr/mpc on :

  1)  x86_64-Linux2.6.18-274.17.1.el5
  2)  x86_64-Linux2.6.32-220.4.1.el6.x86_64
  3)  sparc-SunOS5.10
  4)  plus various others ( ppc970 et al )

seen no major problems thus far. Also, gmp,mpfr,mpc all build fine
with all tests passed even on a very very old :

titan-i386-SunOS5.8 $ uname -X
System = SunOS
Node = titan
Release = 5.8
KernelID = Generic_127722-03
Machine = i86pc
BusType = <unknown>
Serial = <unknown>
Users = <unknown>
OEM# = 0
Origin# = 1
NumCPU = 2

titan-i386-SunOS5.8 $ psrinfo -v
Status of virtual processor 0 as of: 03/12/12 11:47:00
  on-line since 04/28/11 17:39:44.
  The i386 processor operates at 400 MHz,
        and has an i387 compatible floating point processor.
Status of virtual processor 1 as of: 03/12/12 11:47:00
  on-line since 04/28/11 17:39:48.
  The i386 processor operates at 400 MHz,
        and has an i387 compatible floating point processor.
titan-i386-SunOS5.8 $ cat /etc/release
                       Solaris 8 2/02 s28x_u7wos_08a INTEL
           Copyright 2002 Sun Microsystems, Inc.  All Rights Reserved.
                           Assembled 18 December 2001

So I have not seen a gmp mpfr or mpc issue, anywhere.

HOWEVER, I do use the very latest revs of mpfr,gmp and mpc.

dc

-- 
--
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x1D936C72FA35B44B
+-------------------------+-----------------------------------+
| Dennis Clarke           | Solaris and Linux and Open Source |
| dclarke@blastwave.org   | Respect for open standards.       |
+-------------------------+-----------------------------------+

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[NightStrike]

On Mon, Mar 12, 2012 at 5:59 AM, Richard Guenther <rguenther@suse.de> wrote:
> On Wed, 7 Mar 2012, NightStrike wrote:
>
>> On Fri, Mar 2, 2012 at 8:44 AM, Richard Guenther <rguenther@suse.de> wrote:
>> >
>> > GCC 4.7.0 Release Candidate available from gcc.gnu.org
>> >
>> > The first release candidate for GCC 4.7.0 is available from
>> >
>> >  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>> >
>> > and shortly its mirrors.  It has been generated from SVN revision 184777.
>> >
>> > I have so far bootstrapped and tested the release candidate on
>> > x86_64-linux.  Please test it and report any issues to bugzilla.
>> >
>> > If all goes well, I'd like to release 4.7.0 in about three weeks.
>>
>>
>> Building gmp/mpfr/mpc in tree fails in the configure-stage1-mpc step
>> with the current version of mpfr version 3.1.0, out since last
>> October, and mpc, version 0.9, out since Feb of 2011.  I'm guessing
>> the sources moved or something.
>>
>> For instance, just to get the configure step to pass, I had to change
>> the last line of the configure step in the generated Makefile from
>> this:
>>
>>           --disable-shared --with-gmp-include=$$r/$(HOST_SUBDIR)/gmp
>> --with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/.libs
>> --with-mpfr-include=$$s/mpfr
>> --with-mpfr-lib=$$r/$(HOST_SUBDIR)/mpfr/.libs
>>
>> to this:
>>
>>           --disable-shared --with-gmp-include=$$r/$(HOST_SUBDIR)/gmp
>> --with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/.libs
>> --with-mpfr-include=$$s/mpfr/src
>> --with-mpfr-lib=$$r/$(HOST_SUBDIR)/mpfr/.libs
>>
>>
>> The key section is adding /src on the end of --with-mpfr-include=$$s/mpfr/src
>>
>>
>> That gets the build further, but it still doesn't work.
>>
>> This same problem affects 4.6.
>
> The suggested versions of the packages in doc/install.texi are
> older than the ones you tried.
>
> Feel free to propose a patch for trunk, changing the recommended
> versions there.
>
> Richard.

Ok.  But does that mean that to fix configure, we have to increase the
minimum version of mpfr?

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Richard Guenther]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1797 bytes --]

On Wed, 7 Mar 2012, NightStrike wrote:

> On Fri, Mar 2, 2012 at 8:44 AM, Richard Guenther <rguenther@suse.de> wrote:
> >
> > GCC 4.7.0 Release Candidate available from gcc.gnu.org
> >
> > The first release candidate for GCC 4.7.0 is available from
> >
> >  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
> >
> > and shortly its mirrors.  It has been generated from SVN revision 184777.
> >
> > I have so far bootstrapped and tested the release candidate on
> > x86_64-linux.  Please test it and report any issues to bugzilla.
> >
> > If all goes well, I'd like to release 4.7.0 in about three weeks.
> 
> 
> Building gmp/mpfr/mpc in tree fails in the configure-stage1-mpc step
> with the current version of mpfr version 3.1.0, out since last
> October, and mpc, version 0.9, out since Feb of 2011.  I'm guessing
> the sources moved or something.
> 
> For instance, just to get the configure step to pass, I had to change
> the last line of the configure step in the generated Makefile from
> this:
> 
>           --disable-shared --with-gmp-include=$$r/$(HOST_SUBDIR)/gmp
> --with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/.libs
> --with-mpfr-include=$$s/mpfr
> --with-mpfr-lib=$$r/$(HOST_SUBDIR)/mpfr/.libs
> 
> to this:
> 
>           --disable-shared --with-gmp-include=$$r/$(HOST_SUBDIR)/gmp
> --with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/.libs
> --with-mpfr-include=$$s/mpfr/src
> --with-mpfr-lib=$$r/$(HOST_SUBDIR)/mpfr/.libs
> 
> 
> The key section is adding /src on the end of --with-mpfr-include=$$s/mpfr/src
> 
> 
> That gets the build further, but it still doesn't work.
> 
> This same problem affects 4.6.

The suggested versions of the packages in doc/install.texi are
older than the ones you tried.

Feel free to propose a patch for trunk, changing the recommended
versions there.

Richard.

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Marc Glisse]

On Thu, 8 Mar 2012, NightStrike wrote:

> On Wed, Mar 7, 2012 at 10:12 AM, Marc Glisse <marc.glisse@inria.fr> wrote:
>> On Wed, 7 Mar 2012, NightStrike wrote:
>>
>>> Building gmp/mpfr/mpc in tree fails in the configure-stage1-mpc step
>>> with the current version of mpfr version 3.1.0, out since last
>>> October, and mpc, version 0.9, out since Feb of 2011.  I'm guessing
>>> the sources moved or something.
>>
>>
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50461
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51935
>> (second one has a patch)
>
> Does Jonathan Wakely's comment in the second one mean that it won't be fixed?

No, it is an explanation about a workaround (and possibly a reason why it 
is not a blocker), but the main reason it hasn't been fixed is I believe 
that noone has posted a patch to gcc-patches...

-- 
Marc Glisse

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[NightStrike]

On Wed, Mar 7, 2012 at 10:12 AM, Marc Glisse <marc.glisse@inria.fr> wrote:
> On Wed, 7 Mar 2012, NightStrike wrote:
>
>> Building gmp/mpfr/mpc in tree fails in the configure-stage1-mpc step
>> with the current version of mpfr version 3.1.0, out since last
>> October, and mpc, version 0.9, out since Feb of 2011.  I'm guessing
>> the sources moved or something.
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50461
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51935
> (second one has a patch)
>
> --
> Marc Glisse

Does Jonathan Wakely's comment in the second one mean that it won't be fixed?

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Marc Glisse]

On Wed, 7 Mar 2012, NightStrike wrote:

> Building gmp/mpfr/mpc in tree fails in the configure-stage1-mpc step
> with the current version of mpfr version 3.1.0, out since last
> October, and mpc, version 0.9, out since Feb of 2011.  I'm guessing
> the sources moved or something.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50461
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51935
(second one has a patch)

-- 
Marc Glisse

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[NightStrike]

On Fri, Mar 2, 2012 at 8:44 AM, Richard Guenther <rguenther@suse.de> wrote:
>
> GCC 4.7.0 Release Candidate available from gcc.gnu.org
>
> The first release candidate for GCC 4.7.0 is available from
>
>  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>
> and shortly its mirrors.  It has been generated from SVN revision 184777.
>
> I have so far bootstrapped and tested the release candidate on
> x86_64-linux.  Please test it and report any issues to bugzilla.
>
> If all goes well, I'd like to release 4.7.0 in about three weeks.


Building gmp/mpfr/mpc in tree fails in the configure-stage1-mpc step
with the current version of mpfr version 3.1.0, out since last
October, and mpc, version 0.9, out since Feb of 2011.  I'm guessing
the sources moved or something.

For instance, just to get the configure step to pass, I had to change
the last line of the configure step in the generated Makefile from
this:

          --disable-shared --with-gmp-include=$$r/$(HOST_SUBDIR)/gmp
--with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/.libs
--with-mpfr-include=$$s/mpfr
--with-mpfr-lib=$$r/$(HOST_SUBDIR)/mpfr/.libs

to this:

          --disable-shared --with-gmp-include=$$r/$(HOST_SUBDIR)/gmp
--with-gmp-lib=$$r/$(HOST_SUBDIR)/gmp/.libs
--with-mpfr-include=$$s/mpfr/src
--with-mpfr-lib=$$r/$(HOST_SUBDIR)/mpfr/.libs


The key section is adding /src on the end of --with-mpfr-include=$$s/mpfr/src


That gets the build further, but it still doesn't work.

This same problem affects 4.6.

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Kyle Markley]

  On 03/02/12 05:44, Richard Guenther wrote:
> GCC 4.7.0 Release Candidate available from gcc.gnu.org
>
> The first release candidate for GCC 4.7.0 is available from
>
>   ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>
> and shortly its mirrors.  It has been generated from SVN revision 184777.
>
> I have so far bootstrapped and tested the release candidate on
> x86_64-linux.  Please test it and report any issues to bugzilla.
>
> If all goes well, I'd like to release 4.7.0 in about three weeks.

I've been trying to build this on the (unsupported) x86_64 OpenBSD 
platform, but hit an ICE that I have been unable to work around:

internal compiler error: vector VEC(dw_cfi_ref,gc) grow domain error, in 
update_row_reg_save at dwarf2cfi.c:454

I filed this problem, but I'm the only person who has updated it:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52471

As I don't know anything about gcc internals, I'm ill-suited to debug this.

-- 
Kyle Markley

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Michael Hope]

On Sat, Mar 3, 2012 at 2:44 AM, Richard Guenther <rguenther@suse.de> wrote:
>
> GCC 4.7.0 Release Candidate available from gcc.gnu.org
>
> The first release candidate for GCC 4.7.0 is available from
>
>  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>
> and shortly its mirrors.  It has been generated from SVN revision 184777.
>
> I have so far bootstrapped and tested the release candidate on
> x86_64-linux.  Please test it and report any issues to bugzilla.

The RC bootstraps C, C++, Fortran, and Obj-C in arm-linux-gnueabi
Cortex-A9/Thumb-2/NEON/softfp and ARMv5T/ARM/soft-float
configurations.  The test results are here:
 http://builds.linaro.org/toolchain/gcc-4.7.0-RC-20120302/logs/armv7l-natty-cbuild259-tcpanda03-armv5r2/gcc-testsuite.txt
and:
 http://builds.linaro.org/toolchain/gcc-4.7.0-RC-20120302/logs/armv7l-natty-cbuild259-tcpanda02-cortexa9r1/gcc-testsuite.txt

and, on reflection, should be sent to gcc-testresults.  The host
details are in the same directory.

There's a fair number of failures:
 http://people.linaro.org/~michaelh/incoming/a9-faults.txt
 http://people.linaro.org/~michaelh/incoming/armv5-faults.txt

Ramana, any thoughts?  If you ignore the guality and tls ones then
most are testisims but there's a couple of ICEs.

-- Michael

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Ralf Corsepius]

On 03/05/2012 10:12 AM, Richard Guenther wrote:
> On Sat, 3 Mar 2012, Ralf Corsepius wrote:
>
>> On 03/03/2012 02:58 PM, Richard Guenther wrote:
>>> On Sat, Mar 3, 2012 at 11:17 AM, Ralf Corsepius
>>> <ralf.corsepius@rtems.org>   wrote:
>>>> On 03/02/2012 02:44 PM, Richard Guenther wrote:
>>>>>
>>>>> GCC 4.7.0 Release Candidate available from gcc.gnu.org
>>>>>
>>>>> The first release candidate for GCC 4.7.0 is available from
>>>>>
>>>>>    ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>>>>>
>>>>> and shortly its mirrors.  It has been generated from SVN revision
>>>>> 184777.
>>>>>
>>>>> I have so far bootstrapped and tested the release candidate on
>>>>> x86_64-linux.  Please test it and report any issues to bugzilla.
>>>>>
>>>>> If all goes well, I'd like to release 4.7.0 in about three weeks.
>>>>
>>>> Trying to cross-build for sparc-rtems4.11 rpms fails with this:
>>>>
>>>> error: Installed (but unpackaged) file(s) found:
>>>>     /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-ar
>>>>     /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-nm
>>>>     /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-ranlib
>>>>     /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-ar
>>>>     /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-nm
>>>>     /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-ranlib
>>>>
>>>> Are these<target>-gcc-{ar,nm,ranlib} really supposed to be
>>>> installed? Why? The rationale escapes me.
>>>>
>>>> <target>-<target>-gcc-{ar,nm,ranlib} surely is not correct.
>>> Wasn't that fixed? ...
>> Dunno, I used your tarball ;)
>>
>>> In any case, please file a bugreport.
>> Will do so, ASAP.
> Btw, if you can help track down what goes wrong with the
> gcc/Makefile.in:install-gcc-ar rule that would be helpful.
> I think the bug I remember was about Go language binaries.
Correct, go had a similar issue until recently 
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48410) and C++ also had it 
a while (several years?) ago.

Ralf

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Richard Guenther]

On Sat, 3 Mar 2012, Ralf Corsepius wrote:

> On 03/03/2012 02:58 PM, Richard Guenther wrote:
> > On Sat, Mar 3, 2012 at 11:17 AM, Ralf Corsepius
> > <ralf.corsepius@rtems.org>  wrote:
> > > On 03/02/2012 02:44 PM, Richard Guenther wrote:
> > > > 
> > > > 
> > > > GCC 4.7.0 Release Candidate available from gcc.gnu.org
> > > > 
> > > > The first release candidate for GCC 4.7.0 is available from
> > > > 
> > > >   ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
> > > > 
> > > > and shortly its mirrors.  It has been generated from SVN revision
> > > > 184777.
> > > > 
> > > > I have so far bootstrapped and tested the release candidate on
> > > > x86_64-linux.  Please test it and report any issues to bugzilla.
> > > > 
> > > > If all goes well, I'd like to release 4.7.0 in about three weeks.
> > > 
> > > 
> > > Trying to cross-build for sparc-rtems4.11 rpms fails with this:
> > > 
> > > error: Installed (but unpackaged) file(s) found:
> > >    /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-ar
> > >    /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-nm
> > >    /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-ranlib
> > >    /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-ar
> > >    /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-nm
> > >    /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-ranlib
> > > 
> > > Are these<target>-gcc-{ar,nm,ranlib} really supposed to be
> > > installed? Why? The rationale escapes me.
> > > 
> > > <target>-<target>-gcc-{ar,nm,ranlib} surely is not correct.
> > 
> > Wasn't that fixed? ...
> Dunno, I used your tarball ;)
> 
> > In any case, please file a bugreport.
> Will do so, ASAP.

Btw, if you can help track down what goes wrong with the 
gcc/Makefile.in:install-gcc-ar rule that would be helpful.
I think the bug I remember was about Go language binaries.

Richard.

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Dennis Clarke]

> On 03/02/2012 08:40 PM, Dennis Clarke wrote:
>>>>> If all goes well, I'd like to release 4.7.0 in about three weeks.
>>>>
>>>> I'll drop it on Solaris. Give it a push. Do we realy really need that
>>>> ppl/cloog stuff? I have never seen it build and pass any tests, ever,
>>>> even once, on Solaris with or without Sun Studio compilers or GCC or
>>>> prayer and geek magic under a full moon.  Seriously.
>>>
>>> Given that PPL is a C++ library, you need to build it with g++ since
>>> Studio CC and g++ aren't ABI-compatible.
>>>
>>> That said, I'm using them in my Solaris GCC bootstraps, although it
>>> admittedly took some effort to build initially and using it requires you
>>> to jump through hoops to get the configure options right.  I agree that
>>> this is an incredible mess right now.
>>
>> I found it too be entirely too much work to be trusted and considered
>> stable long term. So therefore I generally kick ppl/cloog to the curb
>> and focus on core c,c++ gfortan and ada with objc thrown in without
>> the ppl/cloog bits at all. I have been very happy with my results and
>> the recent 4.6.3 RC was the most clean and pure results I have seen
>> to date, on Solaris 8 old Sparc no less :
>>
>> http://gcc.gnu.org/ml/gcc-testresults/2012-02/msg02786.html
>
> Hi Dennis,
>
> I am planning to update graphite to a newer version of CLooG, which does
> not rely on PPL (but uses isl, a plain c library).
>
> Is the C++ issue the only problem on solaris or are there further
> problems with CLooG? It would be good to know or test this in advance.
> Unfortunately I do not have any solaris machine and there is also none
> on the compile farm. Would you mind testing cloog 0.17 [1] and reporting
> if 'make check' succeeds.
>
> Thanks a lot
> Tobi
>
> [1]
> http://www.bastoul.net/cloog/pages/download/count.php3?url=./cloog-0.17.0.tar.gz
>

be happy to test and grant you an account on servers here.

dc

-- 
--
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x1D936C72FA35B44B
+-------------------------+-----------------------------------+
| Dennis Clarke           | Solaris and Linux and Open Source |
| dclarke@blastwave.org   | Respect for open standards.       |
+-------------------------+-----------------------------------+

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Tobias Grosser]

On 03/02/2012 08:40 PM, Dennis Clarke wrote:
>>>> If all goes well, I'd like to release 4.7.0 in about three weeks.
>>>
>>> I'll drop it on Solaris. Give it a push. Do we realy really need that
>>> ppl/cloog stuff? I have never seen it build and pass any tests, ever,
>>> even once, on Solaris with or without Sun Studio compilers or GCC or
>>> prayer and geek magic under a full moon.  Seriously.
>>
>> Given that PPL is a C++ library, you need to build it with g++ since
>> Studio CC and g++ aren't ABI-compatible.
>>
>> That said, I'm using them in my Solaris GCC bootstraps, although it
>> admittedly took some effort to build initially and using it requires you
>> to jump through hoops to get the configure options right.  I agree that
>> this is an incredible mess right now.
>
> I found it too be entirely too much work to be trusted and considered
> stable long term. So therefore I generally kick ppl/cloog to the curb
> and focus on core c,c++ gfortan and ada with objc thrown in without
> the ppl/cloog bits at all. I have been very happy with my results and
> the recent 4.6.3 RC was the most clean and pure results I have seen
> to date, on Solaris 8 old Sparc no less :
>
> http://gcc.gnu.org/ml/gcc-testresults/2012-02/msg02786.html

Hi Dennis,

I am planning to update graphite to a newer version of CLooG, which does 
not rely on PPL (but uses isl, a plain c library).

Is the C++ issue the only problem on solaris or are there further 
problems with CLooG? It would be good to know or test this in advance. 
Unfortunately I do not have any solaris machine and there is also none 
on the compile farm. Would you mind testing cloog 0.17 [1] and reporting 
if 'make check' succeeds.

Thanks a lot
Tobi

[1] 
http://www.bastoul.net/cloog/pages/download/count.php3?url=./cloog-0.17.0.tar.gz

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Jakub Jelinek]

On Sat, Mar 03, 2012 at 02:04:49PM +0000, Jonathan Wakely wrote:
> > it would be nice to see a fixincl update for 4.6/4.7 to support
> > <bits/string3.h> header as a workaround for PR50916.
> 
> That bug's not even open, pointing it out after the RC has been made
> isn't going to help get it looked at for 4.7.0

The current glibc definitely doesn't have anything like that in the headers,
it uses
__extern_always_inline
and does that for many years (before that glibc headers didn't support the C99
inlines at all, so one would have to use -fgnu89-inline for everything).

	Jakub

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Ralf Corsepius]

On 03/03/2012 02:58 PM, Richard Guenther wrote:
> On Sat, Mar 3, 2012 at 11:17 AM, Ralf Corsepius
> <ralf.corsepius@rtems.org>  wrote:
>> On 03/02/2012 02:44 PM, Richard Guenther wrote:
>>>
>>>
>>> GCC 4.7.0 Release Candidate available from gcc.gnu.org
>>>
>>> The first release candidate for GCC 4.7.0 is available from
>>>
>>>   ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>>>
>>> and shortly its mirrors.  It has been generated from SVN revision 184777.
>>>
>>> I have so far bootstrapped and tested the release candidate on
>>> x86_64-linux.  Please test it and report any issues to bugzilla.
>>>
>>> If all goes well, I'd like to release 4.7.0 in about three weeks.
>>
>>
>> Trying to cross-build for sparc-rtems4.11 rpms fails with this:
>>
>> error: Installed (but unpackaged) file(s) found:
>>    /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-ar
>>    /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-nm
>>    /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-ranlib
>>    /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-ar
>>    /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-nm
>>    /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-ranlib
>>
>> Are these<target>-gcc-{ar,nm,ranlib} really supposed to be
>> installed? Why? The rationale escapes me.
>>
>> <target>-<target>-gcc-{ar,nm,ranlib} surely is not correct.
>
> Wasn't that fixed? ...
Dunno, I used your tarball ;)

> In any case, please file a bugreport.
Will do so, ASAP.

> Yes, those are supposed to be installed, they are ar/nm/ranlib wrappers
> with linker-plugin support.

Hmm, makes me wonder why RH's/Fedora's gcc-4.7.0 doesn't contain them:

# rpm -qlp g/gcc-4.7.0-0.12.fc17.i686.rpm | grep bin
...
/usr/bin/c89
/usr/bin/c99
/usr/bin/cc
/usr/bin/gcc
/usr/bin/gcov
/usr/bin/i686-redhat-linux-gcc

... and what they are useful for? Is there any documentation to learn 
more about them?

Ralf

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Jonathan Wakely]

2012/3/3 Paweł Sikora:
> On Friday 02 of March 2012 14:44:45 Richard Guenther wrote:
>>
>> GCC 4.7.0 Release Candidate available from gcc.gnu.org
>>
>> The first release candidate for GCC 4.7.0 is available from
>>
>>  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>>
>> and shortly its mirrors.  It has been generated from SVN revision 184777.
>>
>> I have so far bootstrapped and tested the release candidate on
>> x86_64-linux.  Please test it and report any issues to bugzilla.
>>
>> If all goes well, I'd like to release 4.7.0 in about three weeks.
>
> it would be nice to see a fixincl update for 4.6/4.7 to support
> <bits/string3.h> header as a workaround for PR50916.

That bug's not even open, pointing it out after the RC has been made
isn't going to help get it looked at for 4.7.0

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Richard Guenther]

On Sat, Mar 3, 2012 at 11:17 AM, Ralf Corsepius
<ralf.corsepius@rtems.org> wrote:
> On 03/02/2012 02:44 PM, Richard Guenther wrote:
>>
>>
>> GCC 4.7.0 Release Candidate available from gcc.gnu.org
>>
>> The first release candidate for GCC 4.7.0 is available from
>>
>>  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>>
>> and shortly its mirrors.  It has been generated from SVN revision 184777.
>>
>> I have so far bootstrapped and tested the release candidate on
>> x86_64-linux.  Please test it and report any issues to bugzilla.
>>
>> If all goes well, I'd like to release 4.7.0 in about three weeks.
>
>
> Trying to cross-build for sparc-rtems4.11 rpms fails with this:
>
> error: Installed (but unpackaged) file(s) found:
>   /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-ar
>   /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-nm
>   /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-ranlib
>   /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-ar
>   /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-nm
>   /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-ranlib
>
> Are these <target>-gcc-{ar,nm,ranlib} really supposed to be
> installed? Why? The rationale escapes me.
>
> <target>-<target>-gcc-{ar,nm,ranlib} surely is not correct.

Wasn't that fixed? ...

In any case, please file a bugreport.

Yes, those are supposed to be installed, they are ar/nm/ranlib wrappers
with linker-plugin support.

Richard.

> Ralf

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Ralf Corsepius]

On 03/02/2012 02:44 PM, Richard Guenther wrote:
>
> GCC 4.7.0 Release Candidate available from gcc.gnu.org
>
> The first release candidate for GCC 4.7.0 is available from
>
>   ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>
> and shortly its mirrors.  It has been generated from SVN revision 184777.
>
> I have so far bootstrapped and tested the release candidate on
> x86_64-linux.  Please test it and report any issues to bugzilla.
>
> If all goes well, I'd like to release 4.7.0 in about three weeks.

Trying to cross-build for sparc-rtems4.11 rpms fails with this:

error: Installed (but unpackaged) file(s) found:
    /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-ar
    /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-nm
    /opt/rtems-4.11/bin/sparc-rtems4.11-gcc-ranlib
    /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-ar
    /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-nm
    /opt/rtems-4.11/bin/sparc-rtems4.11-sparc-rtems4.11-gcc-ranlib

Are these <target>-gcc-{ar,nm,ranlib} really supposed to be
installed? Why? The rationale escapes me.

<target>-<target>-gcc-{ar,nm,ranlib} surely is not correct.

Ralf

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Paweł Sikora]

On Friday 02 of March 2012 14:44:45 Richard Guenther wrote:
> 
> GCC 4.7.0 Release Candidate available from gcc.gnu.org
> 
> The first release candidate for GCC 4.7.0 is available from
> 
>  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
> 
> and shortly its mirrors.  It has been generated from SVN revision 184777.
> 
> I have so far bootstrapped and tested the release candidate on
> x86_64-linux.  Please test it and report any issues to bugzilla.
> 
> If all goes well, I'd like to release 4.7.0 in about three weeks.

it would be nice to see a fixincl update for 4.6/4.7 to support
<bits/string3.h> header as a workaround for PR50916.

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Dennis Clarke]

>>> If all goes well, I'd like to release 4.7.0 in about three weeks.
>>
>> I'll drop it on Solaris. Give it a push. Do we realy really need that
>> ppl/cloog stuff? I have never seen it build and pass any tests, ever,
>> even once, on Solaris with or without Sun Studio compilers or GCC or
>> prayer and geek magic under a full moon.  Seriously.
>
> Given that PPL is a C++ library, you need to build it with g++ since
> Studio CC and g++ aren't ABI-compatible.
>
> That said, I'm using them in my Solaris GCC bootstraps, although it
> admittedly took some effort to build initially and using it requires you
> to jump through hoops to get the configure options right.  I agree that
> this is an incredible mess right now.

I found it too be entirely too much work to be trusted and considered
stable long term. So therefore I generally kick ppl/cloog to the curb
and focus on core c,c++ gfortan and ada with objc thrown in without
the ppl/cloog bits at all. I have been very happy with my results and
the recent 4.6.3 RC was the most clean and pure results I have seen
to date, on Solaris 8 old Sparc no less :

http://gcc.gnu.org/ml/gcc-testresults/2012-02/msg02786.html

>> So really, it that stuff a "need" or a "nice to have" ?
>
> install.texi documents them as optional:
>
> Necessary to build GCC with the Graphite loop optimizations.
>
> but that sentence could probably be clarified.

Would be cool to say "entirely optional".

dc

-- 
--
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x1D936C72FA35B44B
+-------------------------+-----------------------------------+
| Dennis Clarke           | Solaris and Linux and Open Source |
| dclarke@blastwave.org   | Respect for open standards.       |
+-------------------------+-----------------------------------+

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Rainer Orth]

Dennis Clarke <dclarke@blastwave.org> writes:

>> GCC 4.7.0 Release Candidate available from gcc.gnu.org
>>
>> The first release candidate for GCC 4.7.0 is available from
>>
>>  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>>
>> and shortly its mirrors.  It has been generated from SVN revision 184777.
>>
>> I have so far bootstrapped and tested the release candidate on
>> x86_64-linux.  Please test it and report any issues to bugzilla.
>>
>> If all goes well, I'd like to release 4.7.0 in about three weeks.
>
> I'll drop it on Solaris. Give it a push. Do we realy really need that
> ppl/cloog stuff? I have never seen it build and pass any tests, ever,
> even once, on Solaris with or without Sun Studio compilers or GCC or
> prayer and geek magic under a full moon.  Seriously.

Given that PPL is a C++ library, you need to build it with g++ since
Studio CC and g++ aren't ABI-compatible.

That said, I'm using them in my Solaris GCC bootstraps, although it
admittedly took some effort to build initially and using it requires you
to jump through hoops to get the configure options right.  I agree that
this is an incredible mess right now.

> So really, it that stuff a "need" or a "nice to have" ?

install.texi documents them as optional:

Necessary to build GCC with the Graphite loop optimizations.

but that sentence could probably be clarified.

	Rainer

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

Re: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Dennis Clarke]

>
> GCC 4.7.0 Release Candidate available from gcc.gnu.org
>
> The first release candidate for GCC 4.7.0 is available from
>
>  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302
>
> and shortly its mirrors.  It has been generated from SVN revision 184777.
>
> I have so far bootstrapped and tested the release candidate on
> x86_64-linux.  Please test it and report any issues to bugzilla.
>
> If all goes well, I'd like to release 4.7.0 in about three weeks.

I'll drop it on Solaris. Give it a push. Do we realy really need that
ppl/cloog stuff? I have never seen it build and pass any tests, ever,
even once, on Solaris with or without Sun Studio compilers or GCC or
prayer and geek magic under a full moon.  Seriously.

So really, it that stuff a "need" or a "nice to have" ?

dc




-- 
--
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x1D936C72FA35B44B
+-------------------------+-----------------------------------+
| Dennis Clarke           | Solaris and Linux and Open Source |
| dclarke@blastwave.org   | Respect for open standards.       |
+-------------------------+-----------------------------------+

GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Richard Guenther]

GCC 4.7.0 Release Candidate available from gcc.gnu.org

The first release candidate for GCC 4.7.0 is available from

 ftp://gcc.gnu.org/pub/gcc/snapshots/4.7.0-RC-20120302

and shortly its mirrors.  It has been generated from SVN revision 184777.

I have so far bootstrapped and tested the release candidate on
x86_64-linux.  Please test it and report any issues to bugzilla.

If all goes well, I'd like to release 4.7.0 in about three weeks.