public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Rob Emanuele" <rje@cyan.com>
To: "Gcc" <gcc@gcc.gnu.org>
Subject: Optimizations of functions
Date: Wed, 05 Jul 2000 15:34:00 -0000	[thread overview]
Message-ID: <OAEILKBAEOODHMLHNAFFGEBJCBAA.rje@cyan.com> (raw)

I compiling C++ code on an SGI using GCC and I'm trying to
make a debug build with no optimizations.  The code base is
quite large so I'm trying to use as few source files as
possible.

If I specify the -O2 optimize option things compile OK but
are hard to debug.  If I do use not optimizations or
use -O1, I have linking problems that result in messages
like these:

ld32: ERROR 33: Unresolved text symbol
"hsQuat::Read(hsStream *)" -- 1st referenced by
hsKeys.dbg.o.
	Use linker option -v to see when and which objects,
archives and dsos are loaded.
ld32: ERROR 33: Unresolved text symbol
"hsQuat::Write(hsStream *)" -- 1st referenced by
hsKeys.dbg.o.
	Use linker option -v to see when and which objects,
archives and dsos are loaded.
ld32: ERROR 33: Unresolved text symbol "decomp_affine(float
const (*)[3], gemAffineParts *)" -- 1st referenced by
hsKeys.dbg.o.
	Use linker option -v to see when and which objects,
archives and dsos are loaded.
ld32: ERROR 33: Unresolved text symbol
"hsAffineParts::Read(hsStream *)" -- 1st referenced by
hsKeys.dbg.o.
	Use linker option -v to see when and which objects,
archives and dsos are loaded.
ld32: ERROR 33: Unresolved text symbol
"hsAffineParts::Write(hsStream *)" -- 1st referenced by
hsKeys.dbg.o.
	Use linker option -v to see when and which objects,
archives and dsos are loaded.

Does anyone know what single optimization I can turn on to
optimize these out?  I'm pretty sure that none of these
functions are actually used.  At worst does anyone know what
optimizations differ between O1 and O2?

Thanks,

Rob

                 reply	other threads:[~2000-07-05 15:34 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=OAEILKBAEOODHMLHNAFFGEBJCBAA.rje@cyan.com \
    --to=rje@cyan.com \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).