public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net> To: dje@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/4435 Date: Sat, 01 Dec 2001 18:06:00 -0000 [thread overview] Message-ID: <20011202020600.32066.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/4435; it has been noted by GNATS. From: Craig Rodrigues <rodrigc@mediaone.net> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, dje@gcc.gnu.org, gsicherm@elity.com Cc: Subject: Re: libstdc++/4435 Date: Sat, 01 Dec 2001 20:58:46 -0500 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4435&database=gcc This is forwarded from PR 4473. ================================================================================================================== George sent me a followup, but he forgot to cc the GNATS address. I've tried to reply to him since, but there's a mail loop at his end; everything bounces. (The sysadmin there has been informed.) > Date: Wed, 3 Oct 2001 11:32:01 -0400 > From: george@elity.com > To: pme@gcc.gnu.org > Subject: libstdc++/4435 > Reply-To: gsicherm@mail.elity.com > > Thanks for your response. I see now that it's the struct _Rep > itself that is private, not its members. > > I set o-r on all the *.a files -- and the *.la files too just to > be safe. The bug persisted. > > >From the assembler code, the reference to _S_max_size seems to be > in _Rep::_S_create(). It's the same on the Sun, but there I also > find what seem to be linkage declarations for _S_max_size. It's > been a long time since I wrestled with C++; I can't tell whether > _S_max_size really ought to be local or external. > > Maybe it's a thread problem. I didn't mention it in my bug report, > but I'm getting two other undefined externals: .pthread_mutex_lock > and .pthread_mutex_unlock. > > -- > George L. Sicherman > work: gsicherm@elity.com > home: colonel@mail.monmouth.com >
next reply other threads:[~2001-12-02 2:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-01 18:06 Craig Rodrigues [this message] 2001-12-03 10:36 libstdc++/4435 gsicherm
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=20011202020600.32066.qmail@sourceware.cygnus.com \ --to=rodrigc@mediaone.net \ --cc=dje@gcc.gnu.org \ --cc=gcc-prs@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).