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 target/23387] New: Weak support
Date: Sun, 14 Aug 2005 18:59:00 -0000	[thread overview]
Message-ID: <20050814185933.23387.danglin@gcc.gnu.org> (raw)

This PR is a placeholder for known limitations regarding the weak support
of the HP PA_RISC target under HP-UX 11 and later.  This support is available
in GCC 3.3 and later.

Weak support on this target is implemented using SOM secondary definition
(sdef) symbols.  While sdef symbols have some of the attributes of weak
symbols as defined in the ELF SYSV ABI, they differ in behavior in the
following ways:

1) Undefined sdef symbols generate linker and/or runtime errors.
2) The first definition seen by the linker is used (i.e., a primary
   definition doesn't replace an earlier secondary definition).
3) Secondary symbols in objects linked into a shared object become
   primary symbols (sdef symbols never appear in shared objects).

-- 
           Summary: Weak support
           Product: gcc
           Version: 3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: target
        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 target triplet: hppa*-hp-hpux11* (32-bit only)


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


             reply	other threads:[~2005-08-14 18:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14 18:59 danglin at gcc dot gnu dot org [this message]
2005-08-18  3:24 ` [Bug target/23387] " pinskia 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=20050814185933.23387.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).