public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/19212] New: /tmp/ccbY7YyA.s:6435: Error: attempt to get value of unresolved symbol `__s:V151'
Date: Fri, 31 Dec 2004 02:46:00 -0000	[thread overview]
Message-ID: <20041231024632.19212.danglin@gcc.gnu.org> (raw)

/home/dave/gnu/gcc-3.3/objdir/gcc/xgcc -shared-libgcc -B/home/dave/gnu/gcc-3.3/o
bjdir/gcc/ -nostdinc++ -L/home/dave/gnu/gcc-3.3/objdir/vax-ultrix/libstdc++-v3/s
rc -L/home/dave/gnu/gcc-3.3/objdir/vax-ultrix/libstdc++-v3/src/.libs -B/home/dav
e/opt/gnu/vax-ultrix/bin/ -B/home/dave/opt/gnu/vax-ultrix/lib/ -isystem /home/da
ve/opt/gnu/vax-ultrix/include -nostdinc++ -I/home/dave/gnu/gcc-3.3/objdir/vax-ul
trix/libstdc++-v3/include/vax-ultrix -I/home/dave/gnu/gcc-3.3/objdir/vax-ultrix/
libstdc++-v3/include -I../../../../gcc/libstdc++-v3/libsupc++ -I../../../../gcc/
libstdc++-v3/libmath -g -O2 -fno-implicit-templates -Wall -Wno-format -W -Wwrite
-strings -fdiagnostics-show-location=once -c ../../../../gcc/libstdc++-v3/src/lo
cale.cc -o locale.o
/tmp/ccbY7YyA.s: Assembler messages:
/tmp/ccbY7YyA.s:6435: Error: attempt to get value of unresolved symbol `__s:V151
'

This reference comes from the following line in the assembler output:

        .stabs  "__s:V151",38,0,468,__ZNSt6locale13_S_categoriesE

There is no other reference to `__s:V151' in the file.

I have seen this in the past on this target.  I also see unresolved symbols in 
the .stabs output on hppa*-*-hpux* but there the assembler ignores them.

-- 
           Summary: /tmp/ccbY7YyA.s:6435: Error: attempt to get value of
                    unresolved symbol `__s:V151'
           Product: gcc
           Version: 3.3.6
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: debug
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: danglin at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: vax-ultrix


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19212


             reply	other threads:[~2004-12-31  2:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-31  2:46 danglin at gcc dot gnu dot org [this message]
2004-12-31  5:52 ` [Bug debug/19212] " danglin at gcc dot gnu dot org
2005-01-02 19:53 ` danglin at gcc dot gnu dot org
2005-01-03  3:36 ` danglin at gcc dot gnu dot org
2005-01-03 15:26 ` pinskia at gcc dot gnu dot org
2005-01-15 17:27 ` danglin at gcc dot gnu dot org

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=20041231024632.19212.danglin@gcc.gnu.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).