public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/4260: ABI change beween 3.0 and 3.0.1 Date: Mon, 11 Mar 2002 16:06:00 -0000 [thread overview] Message-ID: <20020312000602.28223.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/4260; it has been noted by GNATS. From: "John David Anglin" <dave@hiauly1.hia.nrc.ca> To: phil@jaj.com (Phil Edwards) Cc: gcc-gnats@gcc.gnu.org, dave.anglin@nrc.ca, gcc-bugs@gcc.gnu.org Subject: Re: libstdc++/4260: ABI change beween 3.0 and 3.0.1 Date: Mon, 11 Mar 2002 18:59:08 -0500 (EST) > On Mon, Mar 11, 2002 at 05:02:57PM -0500, John David Anglin wrote: > > > You wrote in the audit trail for this PR that this is now okay. Can we > > > close the PR? > > > > Was any code changed to keep the library internal name and global > > constructors for the library consistent? > > libstdc++ doesn't have any control over the global constructors. Somebody in > compiler-land will have to make changes to collect2 to do this. Looking at the libtool command to build the library in my latest build, I see "-version-info 4:0:0". The generated internal name for the library is "-Wl,+h -Wl,libstdc++.sl.4". However, the global constructors are: _GLOBAL__FI_libstdc___sl_4_0 I don't fully understand how the global constructor names are generated but it is clear that there is a mismatch between the library internal name and the global constructor symbols. In the original report, a change in version from 3.0 to 3.0.1 caused a change in constructor symbol from _GLOBAL__FI_libstdc___sl_3_0 to _GLOBAL__FI_libstdc___sl_3_1 If the libraries were intended to be compatible, the constructor symbol shouldn't have changed. If not, the library internal name should have changed to match. Libtool probably needs to add another digit to the internal names that it generates for the PA som linker so that its precision matches that generated by collect2. However, it also looks like collect2 isn't generating global constructor names correctly. Thus, I don't believe the problem is resolved and we will have the same problem again when there is a minor version change. Dave -- J. David Anglin dave.anglin@nrc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
next reply other threads:[~2002-03-12 0:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-11 16:06 John David Anglin [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-11 14:36 Phil Edwards 2002-03-11 14:06 John David Anglin 2002-03-11 13:46 Phil Edwards
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=20020312000602.28223.qmail@sources.redhat.com \ --to=dave@hiauly1.hia.nrc.ca \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).