From: Al Viro <viro@ZenIV.linux.org.uk>
To: Margit Schubert-While <margitsw@t-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gcc change and kernel build
Date: Sat, 22 Mar 2008 18:37:56 +0000 [thread overview]
Message-ID: <20080322183756.GD10722@ZenIV.linux.org.uk> (raw)
In-Reply-To: <5.1.0.14.2.20080322183805.02769f00@popmail.t-online.de>
On Sat, Mar 22, 2008 at 06:40:03PM +0100, Margit Schubert-While wrote:
> Is this -
> http://marc.info/?l=gcc-bugs&m=120620193114127&w=2
> going to affect kernel builds?
Not unless somebody had decided to use nested functions in the kernel.
I'd ran into only one such, er, person of questionable habits and the
code in question had been long rewritten in C, IIRC. Somebody might
have done that again, but it's not hard to check...
prev parent reply other threads:[~2008-03-22 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 17:40 gcc change and kernel build Margit Schubert-While
2008-03-22 18:35 ` Arjan van de Ven
2008-03-22 18:37 ` Al Viro [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=20080322183756.GD10722@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=margitsw@t-online.de \
/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