From: Pavel Machek <pavel@suse.cz>
To: Linus Torvalds <torvalds@transmeta.com>,
Andrew Morton <andrewm@uow.edu.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] kernel/module.c (plus gratuitous rant)
Date: Fri, 27 Oct 2000 19:45:13 +0200 [thread overview]
Message-ID: <20001027194513.A1060@bug.ucw.cz> (raw)
In-Reply-To: <39F5830E.7963A935@uow.edu.au> <Pine.LNX.4.10.10010241353590.1743-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10010241353590.1743-100000@penguin.transmeta.com>; from Linus Torvalds on Tue, Oct 24, 2000 at 01:55:56PM -0700
Hi!
> > if the person who sent you the -pre4 patch against module.c
> > had Cc:'ed this mailing list then your kernel would do
> > something useful when compiled with gcc-2.7.2.3.
>
> It seems that gcc-2.7.2.3 is terminally ill. I'd rather change
> Documentation/Changes, and just document the fact.
>
> These kinds of subtle work-arounds for gcc bugs are not really acceptable,
> nor is it worthwhile complaining when somebody does development with a gcc
> that is _not_ broken, and doesn't notice that some random gcc bug breaks
> the kernel for others.
Would it be possible to keep 2.7.2.3? You still need 2.7.2.3 to
reliably compile 2.0.X (and maybe even 2.2.all-but-latest?).
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2000-10-27 20:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <39F5830E.7963A935@uow.edu.au>
[not found] ` <Pine.LNX.4.10.10010241353590.1743-100000@penguin.transmeta.com>
2000-10-27 17:45 ` Pavel Machek [this message]
2000-10-27 20:40 ` [patch] kernel/module.c (plus gratuitous rant) Jeff Garzik
2000-10-27 21:12 ` Alan Cox
2000-10-27 20:46 ` Alan Cox
2000-10-28 1:00 ` Keith Owens
2000-10-28 11:15 ` Dominik Kubla
2000-10-29 0:27 ` Richard Henderson
2000-10-29 15:09 ` Dominik Kubla
2000-10-30 11:05 ` Peter Samuelson
2000-10-30 18:50 ` Richard Henderson
2000-10-29 23:23 ` Rusty Russell
2000-10-30 11:08 ` Peter Samuelson
2000-10-30 11:19 ` Recommended compiler? - " Linux Kernel Developer
2000-10-30 11:58 ` Peter Samuelson
2000-10-30 13:49 ` Martin Dalecki
2000-10-30 20:50 ` Horst von Brand
2000-10-30 22:02 ` Jakub Jelinek
2000-10-31 10:27 ` Martin Dalecki
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=20001027194513.A1060@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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;
as well as URLs for NNTP newsgroup(s).