On Friday 02 May 2008 15:11:32 Jakub Jelinek wrote:[snip] I assume the GCC testsuite has the same generic problem, which is probably why it uses the -fdump-tree-optimized parameter to gcc. For example: alistair@just:~$ cat test.c void __attribute__((weak)) func(void) { /* no code */ } int main() { func(); return 0; } alistair@just:~$ gcc -O2 -fdump-tree-optimized test.c alistair@just:~$ rm -f a.out alistair@just:~$ cat test.c*.optimized | egrep "func \\(\\);" func (); Ergo, my compiler isn't buggy. As this doesn't require a runtime test I think it would be OK for the kernel. Of course, whether or not it's worth it is now debatable, given the information Sven-Haegar Koch provided (Debian's GCC version number is actually 4.1.2). -- Cheers, Alistair. 137/1 Warrender Park Road, Edinburgh, UK. --
| Michal Piotrowski | Re: 2.6.23-rc3-mm1 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Fred Tyler | Slow, persistent memory leak in 2.6.20 |
| Roland Dreier | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Antonio Almeida | HTB accuracy for high speed |
