public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Sairam Rangaswamy -X (sairanga - ARICENT TECHNOLOGIES MAURIITIUS LIMITED at Cisco)" <sairanga@cisco.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Undefined symbol .LC531 during linker check gcc 3.4.5-p5 - c++ file compilation/linking
Date: Tue, 16 Sep 2014 05:28:00 -0000	[thread overview]
Message-ID: <60BE056B6E66C549B7498E83642759EB15AD5D83@xmb-rcd-x13.cisco.com> (raw)

Hi,

We are using gcc 3.4.5-p5 compiler for cross compiling. The host is linux machine. The target is MPC8568 or MPC860 based
Powerpc architecture platforms. Target OS is Vxworks.

If I enable the optimization flag, -Os (optimize for space), I get some linker errors during final linker check for
All the binary images generated. The linker check script checks for any unresolved symbols. The error is because
Some symbols are used in the object but not defined and available in any of the binaries. These are
Internal local label related symbols? This is a c++ source file.

objdump -t Alarm.obj | grep .LC
00000000         *UND*  00000000 .LC1531
00000000         *UND*  00000000 .LC1533
00000000         *UND*  00000000 .LC1536
00000000         *UND*  00000000 .LC1535
00000000         *UND*  00000000 .LC1534
00000000         *UND*  00000000 .LC1532

If I don't use the optimization flag, or use -O1 or -O3, there are no errors. 
How do I avoid these extra symbols being generated? What are these symbols.
Unfortunately I am not able to get a reduced file that results in these errors, and
I cannot share the source file as it is proprietary. 


Thanks,
R. Sairam

                 reply	other threads:[~2014-09-16  5:28 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=60BE056B6E66C549B7498E83642759EB15AD5D83@xmb-rcd-x13.cisco.com \
    --to=sairanga@cisco.com \
    --cc=gcc-help@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).