>Matthias, is it possible to switch to gcc-4.6 for m68k but keep
>the gcj part of gcc-defaults at gcj-4.4? Will we be able to both
>use and rebuild gcj-4.4 after switching gcc to gcc-4.6?
Ping on this again, now that I managed to trigger a bug in
gcc’s -fwhole-program --combine for the third or fourth time…
/usr/include/m68k-linux-gnu/bits/string3.h:49: sorry, unimplemented: inlining failed in call to 'memcpy': redefined extern inline functions are not considered for inlining
(luckily, by now, src:mksh knows how to deal with that)
and gcc-4.6 has LTO instead.
>If so… porters, any reason to not switch to gcc-4.6?
Anything? Otherwise I’d say, let’s do it and see what breaks,
but ONLY IF we can keep gcj-4.4 for the time being. But then,
I’m not an m68k porter and don’t believe having the authority
to say so (or the will to be at fault when everything goes up
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh
- Re: gcc-4.6
- From: Ingo Jürgensmann <firstname.lastname@example.org>