From: Willy Tarreau <wtarreau@hera.kernel.org>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4.35.2
Date: Sat, 8 Sep 2007 17:22:27 +0000 [thread overview]
Message-ID: <20070908172227.GA6308@hera.kernel.org> (raw)
I've just released Linux 2.4.35.2.
The removal of -fno-unit-at-a-time in 2.4.35.1 in order to fix build
with gcc-4.2 uncovered nasty optimization issues in the current code
under gcc-4.x. This option not only prevents gcc from reordering
sections, it also prevents it from doing a better optimization of some
inlinable functions and from stripping out static variables which
apparently never get assigned.
Since the removal of the option, some users were caught by modules
which had no symbol for certain parameters ; this is a very annoying
regression which forced them to go back to 2.4.34.x.
So I have restored -fno-unit-at-a-time for now, and yes, it *will* break
gcc-4.2. But the breakage will be detected at build time now, and people
will not get randomly working modules. I am currently exploring several
solutions to this issue, one of them consisting in fixing broken modules
since -fno-unit-at-a-time is already deprecated. If I find something
reasonably non-intrusive, I will consider it for 2.4.36-pre.
Right now, I expect 2.4.35.2 to be safe for gcc-4.1 users.
Willy
--
The patch and changelog will appear soon at the following locations:
ftp://ftp.all.kernel.org/pub/linux/kernel/v2.4/
ftp://ftp.all.kernel.org/pub/linux/kernel/v2.4/patch-2.4.35.2.bz2
ftp://ftp.all.kernel.org/pub/linux/kernel/v2.4/ChangeLog-2.4.35.2
Git repository:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-v2.4.35.y.git
http://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-v2.4.35.y.git
Git repository through the gitweb interface:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-v2.4.35.y.git
Summary of changes from v2.4.35.1 to v2.4.35.2
============================================
Willy Tarreau (3):
i386: do_test_wp_bit() must not be inlined
restore -fno-unit-at-a-time on GCC >= 4
Change VERSION to 2.4.35.2
reply other threads:[~2007-09-08 17:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070908172227.GA6308@hera.kernel.org \
--to=wtarreau@hera.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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