Grant Grundler wrote:
On Sat, Mar 29, 2008 at 06:24:12PM +, rubisher wrote:
...
I looked at gcc-43 build output to check warnings related to networking
as suggest by John David Anglin.
...
That remember me that when I discover those new warnings with gcc-4.2
Hello Grant,
Grant Grundler wrote:
On Wed, Mar 26, 2008 at 10:20:35AM -0600, Grant Grundler wrote:
Another gcc problem report:
That past weekend I built the latest parisc-2.6-25-rc6 kernel from
Kyle's tree using gcc-4.1, gcc-4.2, and gcc-4.3. All three kernels
booted but the networking only
On Wed, Mar 26, 2008 at 10:20:35AM -0600, Grant Grundler wrote:
Another gcc problem report:
That past weekend I built the latest parisc-2.6-25-rc6 kernel from
Kyle's tree using gcc-4.1, gcc-4.2, and gcc-4.3. All three kernels
booted but the networking only worked for gcc-4.1 kernel.
On Wed, Mar 26, 2008 at 10:20:35AM -0600, Grant Grundler wrote:
Another gcc problem report:
That past weekend I built the latest parisc-2.6-25-rc6 kernel from
Kyle's tree using gcc-4.1, gcc-4.2, and gcc-4.3. All three kernels
booted but the networking only worked for gcc-4.1 kernel.
Sorry,
On Tue, Mar 25, 2008 at 06:42:44PM -0400, Carlos O'Donell wrote:
On Sat, Mar 22, 2008 at 6:10 PM, Aurelien Jarno [EMAIL PROTECTED] wrote:
I have tried to build the glibc with GCC 4.3 on hppa, and rpcgen
segfaults when it is used, so the build fails. I haven't start to
investigate the
On Wed, Mar 26, 2008 at 10:20:35AM -0600, Grant Grundler wrote:
Another gcc problem report:
That past weekend I built the latest parisc-2.6-25-rc6 kernel from
Kyle's tree using gcc-4.1, gcc-4.2, and gcc-4.3. All three kernels
booted but the networking only worked for gcc-4.1 kernel.
On Sat, Mar 22, 2008 at 10:02:22PM +0100, Matthias Klose wrote:
amd64 and i386 side note: the gcc-4.3 4.3.0-2 upload has a patch
reenabling the cld instruction when stringops are used; this patch is
neither in the gcc-4_3-branch or in the trunk.
I discussed with doko a bit and have to propose
On Tue, Mar 25, 2008 at 07:54:10AM +, Bastian Blank wrote:
On Sat, Mar 22, 2008 at 10:02:22PM +0100, Matthias Klose wrote:
amd64 and i386 side note: the gcc-4.3 4.3.0-2 upload has a patch
reenabling the cld instruction when stringops are used; this patch is
neither in the gcc-4_3-branch
Bastian Blank a écrit :
On Sat, Mar 22, 2008 at 10:02:22PM +0100, Matthias Klose wrote:
amd64 and i386 side note: the gcc-4.3 4.3.0-2 upload has a patch
reenabling the cld instruction when stringops are used; this patch is
neither in the gcc-4_3-branch or in the trunk.
I discussed with doko
On Tue, Mar 25, 2008 at 09:26:51AM +0100, Pierre Habouzit wrote:
Problem is that memcpy/memmove/memset probably generate rep stos; in
the end, I believe memset/memcpy/memmove to be async signal safe, and
those are inlined fully in many cases.
Please show the sections of POSIX docu or the
On Tue, Mar 25, 2008 at 09:38:32AM +0100, Aurelien Jarno wrote:
Bastian Blank a écrit :
I discussed with doko a bit and have to propose another solution. This
solution have a prequisite: gcc must not generate string ops without
function calls.
This prequisite is not always true. Starting
On Tue, Mar 25, 2008 at 08:39:01AM +, Bastian Blank wrote:
On Tue, Mar 25, 2008 at 09:26:51AM +0100, Pierre Habouzit wrote:
Problem is that memcpy/memmove/memset probably generate rep stos; in
the end, I believe memset/memcpy/memmove to be async signal safe, and
those are inlined
On Sat, Mar 22, 2008 at 6:10 PM, Aurelien Jarno [EMAIL PROTECTED] wrote:
I have tried to build the glibc with GCC 4.3 on hppa, and rpcgen
segfaults when it is used, so the build fails. I haven't start to
investigate the problem (I started by the architectures where the
problems were
On Sun, Mar 23, 2008 at 08:11:31PM +, Matthias Klose wrote:
This will last up to the lenny release, and the toolchain is to be
freezed next week. So I don't ...
... think you'll have to support that patch actively for too long.
wrong, once released with the patch you'll get bug
On Mon, Mar 24, 2008 at 10:36:46AM +0100, Pierre Habouzit wrote:
But unlike others that doesn't seems to care a lot about which
compiler is default in lenny, I would be sad to not see gcc-4.3 our
default compiler. It comes with a lot of enhanced warnings and error
checking, that I've seen
On Sat, Mar 22, 2008 at 10:02:22PM +0100, Matthias Klose wrote:
Matthias Klose writes:
For all ports besides alpha and hppa we plan to make GCC-4.3 the
default compilers for lenny.
amd64 and i386 side note: the gcc-4.3 4.3.0-2 upload has a patch
reenabling the cld instruction when
* Pierre Habouzit:
Isn't it risky for partial upgrades from etch ? Shouldn't we wait for
lenny+1 to revert this ?
I second that, please don't revert the patch until lenny+1. FWIW I
believe the release team as a whole wanted the patch to be kept as well,
but I'll let the other members
On Sun, Mar 23, 2008 at 07:23:10PM +, Florian Weimer wrote:
* Pierre Habouzit:
Isn't it risky for partial upgrades from etch ? Shouldn't we wait for
lenny+1 to revert this ?
I second that, please don't revert the patch until lenny+1. FWIW I
believe the release team as a whole
On Sun, Mar 23, 2008 at 08:23:10PM +0100, Florian Weimer wrote:
What about fixing the etch kernel?
The kernel will get fixed.
Bastian
--
Each kiss is as the first.
-- Miramanee, Kirk's wife, The Paradise Syndrome,
stardate 4842.6
--
To UNSUBSCRIBE, email
On Sun, Mar 23, 2008 at 04:54:29PM +, Matthias Klose wrote:
On Sun, Mar 23, 2008 at 07:15:11AM +, Mike Hommey wrote:
Isn't it risky for partial upgrades from etch ? Shouldn't we wait for
lenny+1 to revert this ?
I second that, please don't revert the patch until lenny+1.
On Sun, Mar 23, 2008 at 07:41:59PM +, Pierre Habouzit wrote:
On Sun, Mar 23, 2008 at 04:54:29PM +, Matthias Klose wrote:
On Sun, Mar 23, 2008 at 07:15:11AM +, Mike Hommey wrote:
Isn't it risky for partial upgrades from etch ? Shouldn't we wait for
lenny+1 to revert this ?
THe _BEST_ example of that are buildd's that for now run etch (even
some sarge not so long time ago) and have a sid chroot to build. Not
keeping the CLD patch means that we break our own buildd infrastructure.
Yay.
No, this is not an argument. If a buildd is used to build packages for
more
IMO the current opinions Isn't it risky, I second that only look
for the risk of running an unfixed kernel (if at all), not of shipping
a compiler diverting in code generation from upstream.
I'm sure all of this is because of the CLD patch:
1,5M gcc-4.2-4.2.3/debian/patches
there's no
This will last up to the lenny release, and the toolchain is to be
freezed next week. So I don't ...
... think you'll have to support that patch actively for too long.
wrong, once released with the patch you'll get bug reports for the
compiler with the patch applied. For every report
* Matthias Klose ([EMAIL PROTECTED]) [080323 21:39]:
This will last up to the lenny release, and the toolchain is to be
freezed next week. So I don't ...
... think you'll have to support that patch actively for too long.
wrong, once released with the patch you'll get bug reports for
For all ports besides alpha and hppa we plan to make GCC-4.3 the
default compilers for lenny.
- both alpha and hppa show regressions in the glibc testsuite when
built with GCC-4.3
- gcj has a lot of regressions in 4.3 on alpha (but doesn't work in
4.2 either).
- gij/gcj shows bus
Matthias Klose writes:
For all ports besides alpha and hppa we plan to make GCC-4.3 the
default compilers for lenny.
amd64 and i386 side note: the gcc-4.3 4.3.0-2 upload has a patch
reenabling the cld instruction when stringops are used; this patch is
neither in the gcc-4_3-branch or in the
On Sat, Mar 22, 2008 at 4:33 PM, Matthias Klose [EMAIL PROTECTED] wrote:
For all ports besides alpha and hppa we plan to make GCC-4.3 the
default compilers for lenny.
- both alpha and hppa show regressions in the glibc testsuite when
built with GCC-4.3
What is the list of regressions?
Carlos O'Donell writes:
- gij/gcj shows bus errors on hppa (either 4.2 or 4.3).
Has gij/gcj ever worked on hppa-linux?
at least the gij/gcj before adding support for generics (1.5) did
work. Now that a working runtime is required for the compiler makes
things different. Please try to run
On Sat, Mar 22, 2008 at 5:10 PM, Matthias Klose [EMAIL PROTECTED] wrote:
Carlos O'Donell writes:
- gij/gcj shows bus errors on hppa (either 4.2 or 4.3).
Has gij/gcj ever worked on hppa-linux?
at least the gij/gcj before adding support for generics (1.5) did
work. Now that a
Carlos O'Donell writes:
On Sat, Mar 22, 2008 at 5:10 PM, Matthias Klose [EMAIL PROTECTED] wrote:
Carlos O'Donell writes:
- gij/gcj shows bus errors on hppa (either 4.2 or 4.3).
Has gij/gcj ever worked on hppa-linux?
at least the gij/gcj before adding support for generics
On Sat, Mar 22, 2008 at 6:10 PM, Aurelien Jarno [EMAIL PROTECTED] wrote:
Carlos O'Donell a écrit :
On Sat, Mar 22, 2008 at 4:33 PM, Matthias Klose [EMAIL PROTECTED] wrote:
For all ports besides alpha and hppa we plan to make GCC-4.3 the
default compilers for lenny.
- both alpha
32 matches
Mail list logo
