From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Mikael Pettersson <mikpe@user.it.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gcc-3.4.0 patches for 2.4.27?
Date: Wed, 28 Apr 2004 11:14:02 -0300 [thread overview]
Message-ID: <20040428141402.GA14403@logos.cnet> (raw)
In-Reply-To: <16527.45935.480630.490196@alkaid.it.uu.se>
On Wed, Apr 28, 2004 at 03:36:47PM +0200, Mikael Pettersson wrote:
> Marcelo,
>
> Will you accept patches allowing gcc-3.4.0 to compile
> 2.4.27 or not? I can understand if you want to be
> conservative and not change _anything_ if you don't have to.
>
> gcc-3.4.0 errors out in 2.4.27-pre1 due to (a) inconsistent
> FASTCALL declarations, (b) uninlinable inlines, and (c)
> -funit-at-a-time which seems to leave unresolved calls to
> strcpy() around [gcc optimises sprintf "%s" to strcpy()].
> There are also tons of warnings due to cast-as-lvalue
> and "+m" asm() constraints.
>
> I currently have a 40KB+ patch for 2.4.27-pre1 which works
> for me on i386, UP and SMP. The changes are all backports
> from 2.6. I'll do x86_64 and ppc(32) in a few days.
>
> http://www.csd.uu.se/~mikpe/linux/patches/2.4/patch-gcc340-fixes-2.4.27-pre1
> is the location of the current version.
Hi Mikael,
The patch looks alright for me, but I better see reviews from
other people.
Since v2.4 is in feature freeze, I have a reason not to apply it.
I'm not sure. Lets wait a while and see.
next prev parent reply other threads:[~2004-04-28 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 13:36 gcc-3.4.0 patches for 2.4.27? Mikael Pettersson
2004-04-28 14:14 ` Marcelo Tosatti [this message]
2004-05-01 14:00 ` Denis Vlasenko
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=20040428141402.GA14403@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@user.it.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.