public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dave.anglin@nrc.ca
To: gcc-gnats@gcc.gnu.org
Subject: c++/8512: libstdc++-v3 fails to build with HP assembler
Date: Sat, 09 Nov 2002 10:06:00 -0000 [thread overview]
Message-ID: <20021109175845.25877.qmail@sources.redhat.com> (raw)
>Number: 8512
>Category: c++
>Synopsis: libstdc++-v3 fails to build with HP assembler
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Nov 09 10:06:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Dave Anglin
>Release: gcc-3.3 (experimental)
>Organization:
>Environment:
hppa64-hp-hpux11.11. The problem also likely affects hppa2.0-hp-hpux11*.
>Description:
/xxx/gnu/gcc-3.3/objdir/gcc/xgcc -shared-libgcc -B/xxx/gnu/gcc-3.3/objdir/gcc/ -
nostdinc++ -L/xxx/gnu/gcc-3.3/objdir/hppa64-hp-hpux11.11/libstdc++-v3/src -L/xxx
/gnu/gcc-3.3/objdir/hppa64-hp-hpux11.11/libstdc++-v3/src/.libs -B/opt/gnu64/hppa
64-hp-hpux11.11/bin/ -B/opt/gnu64/hppa64-hp-hpux11.11/lib/ -isystem /opt/gnu64/h
ppa64-hp-hpux11.11/include -I../../../../gcc/libstdc++-v3/../gcc -I../../../../g
cc/libstdc++-v3/../include -I/xxx/gnu/gcc-3.3/objdir/hppa64-hp-hpux11.11/libstdc
++-v3/include/hppa64-hp-hpux11.11 -I/xxx/gnu/gcc-3.3/objdir/hppa64-hp-hpux11.11/
libstdc++-v3/include -I../../../../gcc/libstdc++-v3/libsupc++ -g -O2 -fno-implic
it-templates -Wall -Wno-format -W -Wwrite-strings -Winline -fdiagnostics-show-lo
cation=once -g -c ../../../../gcc/libstdc++-v3/libsupc++/eh_aux_runtime.cc
cc1plus: warning: -g is only supported when using GAS on this processor,
cc1plus: warning: -g option disabled
as: error 7403: undefined label - _ZTISt8bad_cast (7403)
On the PA under hpux, undefined external symbols need to
be "imported" to set the type of the symbol. If this isn't
done, the dynamic loader won't be able to resolve the
address of the symbol correctly. The HP SOM linker is
also known to dump core if a P fixup occurs for a data
symbol that should be a function symbol.
The GNU assembler doesn't treat the above as an error but the executable may malfunction in a subtle way. Thus, this needs to be fixed for correct operation with the GNU assembler as well.
This appears to be a regression from 3.0.2 where we had
similar problems with typeinfo nodes in the regression fix phase.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2002-11-09 18:06 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=20021109175845.25877.qmail@sources.redhat.com \
--to=dave.anglin@nrc.ca \
--cc=gcc-gnats@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).