Re: GCC 3.3 can't inline?!
On Thu, 22 May 2003 about 14:05 +0900 UTC Stephen J. Turnbull wrote:
Or something like that; it's possible my tree is corrupt or
somebody
"touched" inline.c with the gripping hand, but gcc 3.2 is still fine.
Anyway, _nothing_ inlines as far as I can tell; I get dozens of these:
gcc -c -Wall -Wno-switch -Winline -Wmissing-prototypes -Wsign-compare -Wundef
-Wstrict-prototypes -Wpacked -Wshadow -Wmissing-declarations -g -O3 -Demacs -I.
-DHAVE_CONFIG_H -I/usr/X11R6/include /playpen/Projects/XEmacs/21.5/src/fileio.c
/playpen/Projects/XEmacs/21.5/src/fileio.c: In function `Ffile_name_as_directory':
/playpen/Projects/XEmacs/21.5/src/fileio.c:266: warning: inlining failed in call to
`Ffind_file_name_handler'
/playpen/Projects/XEmacs/21.5/src/fileio.c:524: warning: called from here
from every file compiled.
Debian `sid', updated yesterday, gcc3.3_3.3-2 Debian package.
Using configure --compiler=/usr/bin/gcc-3.2 wins, so I think it's
either soemthing to do with GCC 3.3 or with Debian's package version.
I see the same with any gnu-compiled gcc after 3.2 but not with Apple's 3.3
snapshot of late Jan. 2003. That was before some great gcc merge. Also, on
my Mac if I compile 21.5.b13 with a May 5-10 3.4 (the one I use most often,
now) with the warnings turned on, it usually causes a bus error during the
compilation process. (gnu 3.3 did too, but I used it only a few times).
Compiling beta software with beta compilers, often using beta libraries on a
beta operating system--it still works better than my office IBM running
Win2K. But mileage (or kilometrics) varies.
--
Dr. Robert Delius Royar Associate Professor of English
Morehead State University Morehead, Kentucky
Kill UGLY Corporate Radio
Space aliens are stealing American jobs.
-Paul Krugman (MIT)