|| ||Willy Tarreau <firstname.lastname@example.org>|
|| ||Linux 18.104.22.168|
|| ||Sat, 8 Sep 2007 17:22:27 +0000|
I've just released Linux 22.214.171.124.
The removal of -fno-unit-at-a-time in 126.96.36.199 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 188.8.131.52 to be safe for gcc-4.1 users.
The patch and changelog will appear soon at the following locations:
Git repository through the gitweb interface:
Summary of changes from v184.108.40.206 to v220.127.116.11
Willy Tarreau (3):
i386: do_test_wp_bit() must not be inlined
restore -fno-unit-at-a-time on GCC >= 4
Change VERSION to 18.104.22.168
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/