From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.4.31 0/9] gcc4 fixes overview
Date: Mon, 13 Jun 2005 10:42:11 -0300 [thread overview]
Message-ID: <20050613134211.GA23160@logos.cnet> (raw)
In-Reply-To: <200506121116.j5CBGJPs019683@harpo.it.uu.se>
Hi Mikael,
I believe its about time for v2.4 to reject such kind of modifications,
they can live outside the mainline repository.
On Sun, Jun 12, 2005 at 01:16:19PM +0200, Mikael Pettersson wrote:
> This set of patches fixes gcc4 problems in the 2.4.31
> kernel's 'core' code. I've been running gcc4-compiled 2.4
> kernels for several months on i386, x86_64, and ppc32, and
> there are currently no known regressions compared to gcc34.
>
> Note: you'll want to use recent gcc-4.0.1 snapshots as
> gcc-4.0.0 is known to be broken.
>
> This set of patches do not include fixes to drivers,
> file systems, or architectures I don't use myself. I
> have a preliminary patch kit for those, but as it
> has received only limited compile testing I'm not
> submitting it unless these core patches are accepted.
>
> The patch set consists of the following 9 parts:
> [1/9] fix incomplete array errors
> [2/9] fix static-vs-nonstatic redefinition errors
> [3/9] fix nested function declaration errors
> [4/9] fix undefined strcpy linkage errors
> [5/9] fix x86_64 acpi assembly error
> [6/9] fix x86_64 sys_iopl() bug
> [7/9] fix const function warnings
> [8/9] silence pointer signedness warnings
> [9/9] fix i386 struct_cpy() warnings
prev parent reply other threads:[~2005-06-13 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-12 11:16 [PATCH 2.4.31 0/9] gcc4 fixes overview Mikael Pettersson
2005-06-13 13:42 ` Marcelo Tosatti [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050613134211.GA23160@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox