GCC 4.7 is now the default for x86 architectures
 

Matthias Klose dixit:

>GCC 4.7 is now the default for x86 architectures for all frontends except the D
>frontends, including KFreeBSD and the Hurd.

How are the plans for other architectures?

The m68k status (which obviously can’t influence the release decisions)
is as follows: gcc-4.7 builds, last time I looked gcj-4.7 didn’t but it
is currently building again (so let’s see whether it does this time);
gcc-4.6 and gnat-4.6 are getting development and bugfixes (I’ve queued
up some patches, but am not entirely ready with all of them, plus some
for binutils and gdb), and I’ve asked for help re. the gcj-4.4/gcj-4.6
recent problems. But nothing has tested gcj-4.7, and I fear of new and
old bugs… so I’d rather not switch default compiler to it anytime soon.

As for gcc-4.7 in general: a friend (authoring an ObjC framework _and_
runtime) told me that it dropped support for an old method of doing
things while not fulfilling the promise to get the new method of doing
it (don’t exactly remember what it was, /msg js on freenode for details)
fixed, with the effect that gobjc-4.7 is virtually useless/broken.

This is hearsay, but ask him for details, and check them against
reality.

bye,
//mirabilos
--
Yay for having to rewrite other people's Bash scripts because bash
suddenly stopped supporting the bash extensions they make use of
-- Tonnerre Lombard in #nosec


--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: Pine.BSM.4.64L.1205071730550.28104@herc.mirbsd.org ">http://lists.debian.org/Pine.BSM.4.64L.1205071730550.28104@herc.mirbsd.org

GCC 4.7 is now the default for x86 architectures
 

On 07.05.2012 19:35, Thorsten Glaser wrote:
> Matthias Klose dixit:
>
>> GCC 4.7 is now the default for x86 architectures for all frontends except the D
>> frontends, including KFreeBSD and the Hurd.
>
> How are the plans for other architectures?

I don't have plans to change any other architectures. If a port is not a release
architectures (and port maintainers don't plan to make it a release
architecture), people can change the default at any time from my point of view.

> As for gcc-4.7 in general: a friend (authoring an ObjC framework _and_
> runtime) told me that it dropped support for an old method of doing
> things while not fulfilling the promise to get the new method of doing
> it (don’t exactly remember what it was, /msg js on freenode for details)
> fixed, with the effect that gobjc-4.7 is virtually useless/broken.
>
> This is hearsay, but ask him for details, and check them against
> reality.

I didn't rely on hearsay, but did ask the GNUstep maintainers for feedback.
Please join the Debian GNUstep package maintainers ML if you want to add
something, or review the past discussion.

Matthias


--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4FA80A89.8070002@debian.org">http://lists.debian.org/4FA80A89.8070002@debian.org

GCC 4.7 is now the default for x86 architectures
 

Hi,

Matthias Klose wrote:
> On 07.05.2012 19:35, Thorsten Glaser wrote:
>> Matthias Klose dixit:
>>
>>> GCC 4.7 is now the default for x86 architectures for all frontends except the D
>>> frontends, including KFreeBSD and the Hurd.
>>
>> How are the plans for other architectures?

About ppc64 port, because of FTBFS (#668861),
build-tests by gcc-4.7 cannot be done at all
even at experimental repository by gcc-defaults 1.116exp1.

Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC


--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4FA919A6.1090507@gmail.com">http://lists.debian.org/4FA919A6.1090507@gmail.com