Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!yarrina.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!Germany.EU.net!news.dfn.de!zrz.TU-Berlin.DE!cs.tu-berlin.de!informatik.uni-bremen.de!nordwest.pop.de!uniol!uni-erlangen.de!uni-regensburg.de!news.uni-stuttgart.de!schweikh From: schweikh@zeiss.ito.uni-stuttgart.de (Jens Schweikhardt) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Why won't kernel compile with COPTFLAGS=-O3 Date: 4 Dec 1995 12:42:40 GMT Organization: Comp.Center (RUS), U of Stuttgart, FRG Lines: 18 Message-ID: <49uqc0$1f5s@info4.rus.uni-stuttgart.de> NNTP-Posting-Host: zeiss.ito.uni-stuttgart.de Hello, recently I tried to compile 2.1.0 with a modification in Makefile.i386 where I changed the COPTFLAGS (sp?) from -O to -m486 -O3. At the link stage the make stopped due to undefined symbols _dummyinit (init_main.o) and _dummy_cleanup. Looking at the source in init_main.c, dummyinit() seems to be an empty function which might be optimized out of existence by -O3. I've tried -O3 with -fkeep-inline-functions but to no avail. I believe there's some strange symbol table hacking going on. Is there any way to get a kernel compiled with -O3? Or maybe I should complain to the gcc maintainers? Thanks for casting some light on the issue. Bye, Jens -- SIGSIG -- signature too long (core dumped)