This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: [Proposed binutils PATCH] Re: Diagnosing an intricate C++ problem
- To: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Subject: Re: [Proposed binutils PATCH] Re: Diagnosing an intricate C++ problem
- From: Jason Merrill <jason at redhat dot com>
- Date: 02 Sep 2000 23:12:20 -0700
- Cc: rittle at rsch dot comm dot mot dot com, gcc-patches at gcc dot gnu dot org, binutils at sources dot redhat dot com
- References: <Pine.BSF.4.21.0009021957530.89194-100000@taygeta.dbai.tuwien.ac.at>
>>>>> Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:
> Yes (and sorry that it took that long): My production stuff linked
> successfully, but produced tons of warnings.
> Here is a minimal test case
> ---- cut: x.cc ----
> #include <string>
> #include <vector>
> main() {
> vector<string> w;
> w.push_back("Hello");
> }
> ---- cut: x.cc----
> for which a simple `g++ x.cc` generates the following warnings:
Well, of course it does. You're compiling it with different flags than
were used to build libstdc++, so the generated code is different. That's
why this feature is pretty useless for code.
Jason