From: "Rich Baum" <baumr1@coral.indstate.edu>
To: Andreas Franck <afranck@gmx.de>,
Linus Torvalds <torvalds@transmeta.com>,
Mike Galbraith <mikeg@wen-online.de>,
linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@transmeta.com>,
Mike Galbraith <mikeg@wen-online.de>
Subject: Re: [revisited] Oops on boot with 2.4.0testX and GCC snapshots
Date: Mon, 1 Jan 2001 17:28:11 -0500 [thread overview]
Message-ID: <3A50BE2B.11580.104406@localhost> (raw)
In-Reply-To: <01010119004100.01545@dg1kfa.ampr.org>
On 1 Jan 2001, at 19:00, Andreas Franck wrote:
> Hello together,
>
> after all the new year's celebrations, I have today taken the time to create
> a small patch, based on Linus' idea, that will fix this problem in the
> kernel, _without_ pessimizing any code or breaking with earlier compilers.
>
> 2.4.0-prerelease is now running here for an hour compiled completely with
> gcc-snapshot-2.97-20001222, without any noticed problems (so far).
>
> Perhaps this could be included in the kernel to enable people to look for the
> real caveats when compiling everything on the bleeding edge, or should we
> wait for the GCC maintainers' call - I haven't had any reaction on my bug
> report yet.
>
> Along with it is a small fix for a typo in fs/umsdos/mangle.c, which was
> detected by GCC's new preprocessor (#elseif instead of #else).
>
> Greetings and a happy new year to everyone,
> Andreas
>
> --
> ->>>----------------------- Andreas Franck --------<<<-
> ---<<<---- Andreas.Franck@post.rwth-aachen.de --->>>---
> ->>>---- Keep smiling! ----------------------------<<<-
>
Thanks, this patch works for me. I'm using gcc-2.97-20001225.
-
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/
prev parent reply other threads:[~2001-01-01 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-01 18:00 [revisited] Oops on boot with 2.4.0testX and GCC snapshots Andreas Franck
2001-01-01 22:28 ` Rich Baum [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=3A50BE2B.11580.104406@localhost \
--to=baumr1@coral.indstate.edu \
--cc=afranck@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
--cc=richbaum@acm.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