public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> To: jason@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/6611: [PATCH] Non-weak emission of `std::__default_alloc_template[...]' on platform(s) where it should be weak Date: Tue, 21 May 2002 08:23:00 -0000 [thread overview] Message-ID: <20020521151607.2179.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/6611; it has been noted by GNATS. From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> To: Jason Merrill <jason@redhat.com>, "B. Kosnik" <bkoz@nabi.net> Cc: gcc-gnats@gcc.gnu.org, <gcc-patches@gcc.gnu.org>, <bkoz@redhat.com>, <gcc-bugs@gcc.gnu.org>, <ljrittle@acm.org> Subject: Re: c++/6611: [PATCH] Non-weak emission of `std::__default_alloc_template[...]' on platform(s) where it should be weak Date: Tue, 21 May 2002 12:56:26 +0200 (CEST) On Sat, 18 May 2002, Jason Merrill wrote: > Tested i686-pc-linux-gnu, applied to trunk. I'll come up with a testcase > soon, but I want to get this in now so it stops interfering with libstdc++ > work. Thanks! I can confirm this fixes the bug I have been experiencing (and which was destilled into the testcase in PR c++/6611). One way to come up with a testcase, as suggested by Loren, would be to duplicate the file in the PR and simply rename all classes in that copy; if linking both object files fails, this is due to this/a bug. Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next reply other threads:[~2002-05-21 15:23 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-21 8:23 Gerald Pfeifer [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-18 8:06 B. Kosnik 2002-05-17 21:46 Jason Merrill
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=20020521151607.2179.qmail@sources.redhat.com \ --to=pfeifer@dbai.tuwien.ac.at \ --cc=gcc-prs@gcc.gnu.org \ --cc=jason@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).