On Thu, Jun 13, 2013 at 02:51:43PM +0200, Matthias Klose wrote:
GCC 4.8 is now the default on all x86 architectures, and on all ARM
architectures (the latter confirmed by the Debian ARM porters).
GCC 4.8 seems fine on s390x, it can build a running Linux kernel. On
s390 something weird happened
On 14-06-13 21:11, Thorsten Glaser wrote:
Wouter, Mikael: input on switching C/C++ to 4.8?
We don't have much data either way, do we?
I suppose it shouldn't be too much of a problem, but I can't be sure. In
the past we've usually taken the plunge, and filed bugs if things go
really bad.
--
On Tue, Jun 18, 2013 at 8:02 PM, John David Anglin dave.ang...@bell.net wrote:
Hi Aurelien,
On 18-Jun-13, at 6:05 PM, Aurelien Jarno wrote:
This is true that they have recently contacted me through another email
address, but I haven't found time to work on that. Just stay tuned.
That's
On Fri, Jun 14, 2013 at 01:12:30PM +0200, Matthias Klose wrote:
Am 13.06.2013 16:46, schrieb Steven Chamberlain:
Hi,
On 13/06/13 13:51, Matthias Klose wrote:
GCC 4.8 is now the default on all x86 architectures, and on all ARM
architectures (the latter confirmed by the Debian ARM
Hi Aurelien,
On 18-Jun-13, at 6:05 PM, Aurelien Jarno wrote:
This is true that they have recently contacted me through another
email
address, but I haven't found time to work on that. Just stay tuned.
That's great news.
Helge and I have been working away as best we can to maintain the
Am 15.06.2013 03:22, schrieb Stephan Schreiber:
GCC-4.8 should become the default on ia64 soon; some other changes are
desirable:
- The transition of gcc-4.8/libgcc1 to libunwind8.
- A removal of the libunwind7 dependency of around 4600 packages on ia64 -
when
they are updated next time
Am 13.06.2013 21:47, schrieb Thorsten Glaser:
Matthias Klose dixit:
The Java and D frontends now default to 4.8 on all architectures, the Go
frontend stays at 4.7 until 4.8 get the complete Go 1.1 support.
I’d like to have gcj at 4.6 in gcc-defaults for m68k please,
until the 4.8 one
Am 13.06.2013 16:46, schrieb Steven Chamberlain:
Hi,
On 13/06/13 13:51, Matthias Klose wrote:
GCC 4.8 is now the default on all x86 architectures, and on all ARM
architectures (the latter confirmed by the Debian ARM porters). I did not
get
any feedback from other port maintainers, so
Matthias Klose dixit:
I’d like to have gcj at 4.6 in gcc-defaults for m68k please,
until the 4.8 one stops FTBFSing.
please send a patch.
For gcc-defaults? I think that one is trivial…
For gcj? I did not take Compiler Design in what two semesters
of Uni I managed until I ran out of money. I
GCC-4.8 should become the default on ia64 soon; some other changes are
desirable:
- The transition of gcc-4.8/libgcc1 to libunwind8.
- A removal of the libunwind7 dependency of around 4600 packages on
ia64 - when they are updated next time after the transition. The
libc6.1 should (likely)
Am 07.05.2013 15:25, schrieb Matthias Klose:
The decision when to make GCC 4.8 the default for other architectures is
left to the Debian port maintainers.
[...]
Information on porting to GCC 4.8 from previous versions of GCC can be
found in the porting guide
Hi,
On 13/06/13 13:51, Matthias Klose wrote:
GCC 4.8 is now the default on all x86 architectures, and on all ARM
architectures (the latter confirmed by the Debian ARM porters). I did not get
any feedback from other port maintainers, so unless this does change and port
maintainers get
Am Donnerstag, den 13.06.2013, 15:46 +0100 schrieb Steven Chamberlain:
Hi,
On 13/06/13 13:51, Matthias Klose wrote:
GCC 4.8 is now the default on all x86 architectures, and on all ARM
architectures (the latter confirmed by the Debian ARM porters). I did not
get
any feedback from
Matthias Klose dixit:
The Java and D frontends now default to 4.8 on all architectures, the Go
frontend stays at 4.7 until 4.8 get the complete Go 1.1 support.
I’d like to have gcj at 4.6 in gcc-defaults for m68k please,
until the 4.8 one stops FTBFSing.
From me nothing against switching C/C++
14 matches
Mail list logo
