From: Russell King <rmk@arm.linux.org.uk>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Andrzej Krzysztofowicz <kufel!ankry@green.mif.pg.gda.pl>,
Matan Ziv-Av <matan@svgalib.org>, mythos <papadako@csd.uoc.gr>,
linux-kernel@vger.kernel.org
Subject: Re: Can't compile 2.4.3 with agcc
Date: Tue, 24 Apr 2001 09:53:04 +0100 [thread overview]
Message-ID: <20010424095304.A2389@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200104232232.AAA12700@kufel.dom> <Pine.LNX.4.33.0104232349530.15177-100000@imladris.demon.co.uk>
In-Reply-To: <Pine.LNX.4.33.0104232349530.15177-100000@imladris.demon.co.uk>; from dwmw2@infradead.org on Mon, Apr 23, 2001 at 11:54:10PM +0100
On Mon, Apr 23, 2001 at 11:54:10PM +0100, David Woodhouse wrote:
> On Tue, 24 Apr 2001, Andrzej Krzysztofowicz wrote:
> > - extern void __buggy_fxsr_alignment(void);
> > - __buggy_fxsr_alignment();
> > + extern void __BUG__task_struct__data_is_not_properly_alligned__Probably_your_compiler_is_buggy(void);
> > + __BUG__task_struct__data_is_not_properly_alligned__Probably_your_compiler_is_buggy();
>
> 1. People would probably still report that to l-k instead of reading it.
> 2. It's still not guaranteed to compile, even with correct compilers.
>
> Maybe you can do a post-processing step - a sanity check which is run
> _after_ build. But the runtime check is sufficient. People won't randomly
> start compiling kernels for production boxen with silly compilers, then
> booting them unattended. And if they do, they deserve the downtime.
grep '__BUG__' System.map | cut -d\ -f3
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-04-24 8:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 13:13 Can't compile 2.4.3 with agcc mythos
2001-04-23 14:48 ` Russell King
2001-04-23 15:27 ` Alan Cox
2001-04-23 15:52 ` David Woodhouse
2001-04-23 17:57 ` Ingo Oeser
2001-04-23 19:43 ` Alan Cox
2001-04-23 20:46 ` David Woodhouse
2001-04-23 21:03 ` Matan Ziv-Av
2001-04-23 21:16 ` David Woodhouse
2001-04-23 22:32 ` Andrzej Krzysztofowicz
2001-04-23 22:54 ` David Woodhouse
2001-04-24 8:53 ` Russell King [this message]
2001-04-24 12:37 ` David Woodhouse
2001-04-23 22:25 ` Horst von Brand
2001-04-23 22:35 ` David Woodhouse
2001-04-24 13:28 ` Horst von Brand
2001-04-24 13:30 ` David Woodhouse
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=20010424095304.A2389@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=dwmw2@infradead.org \
--cc=kufel!ankry@green.mif.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=matan@svgalib.org \
--cc=papadako@csd.uoc.gr \
/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.