From: David Woodhouse <dwmw2@infradead.org>
To: Matan Ziv-Av <matan@svgalib.org>
Cc: Russell King <rmk@arm.linux.org.uk>, mythos <papadako@csd.uoc.gr>,
linux-kernel@vger.kernel.org
Subject: Re: Can't compile 2.4.3 with agcc
Date: Mon, 23 Apr 2001 22:16:05 +0100 [thread overview]
Message-ID: <2835.988060565@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21_heb2.09.0104232359390.2200-100000@matan.home>
In-Reply-To: <Pine.LNX.4.21_heb2.09.0104232359390.2200-100000@matan.home>
matan@svgalib.org said:
> This is known at compile time, right? Would it not be better to
> replace the printk with #error ? Why do I need to boot the bad kernel
> to find out that it does not work, when it is known when compiling?
It's known at compile time, but not at preprocessing time, so it can't be
done with #error. If you can come up with a way of doing it at compile time
such that:
1. It's _guaranteed_ to work when the compiler does align the members
of the structure as we desire.
2. It gives a message sufficiently informative that it prevents further
such reports getting to l-k.
... then I agree, it would be better to do it at compile time. If not, the
runtime check is the best we can do.
We really ought to have learned by now that we shouldn't be relying on the
observed behaviour of this week's compiler in this particular phase of the
moon.
--
dwmw2
next prev parent reply other threads:[~2001-04-23 21:16 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 [this message]
2001-04-23 22:32 ` Andrzej Krzysztofowicz
2001-04-23 22:54 ` David Woodhouse
2001-04-24 8:53 ` Russell King
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=2835.988060565@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matan@svgalib.org \
--cc=papadako@csd.uoc.gr \
--cc=rmk@arm.linux.org.uk \
/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