This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [v3] libstdc++/54296
- From: Paolo Carlini <paolo dot carlini at oracle dot com>
- To: François Dumont <frs dot dumont at gmail dot com>
- Cc: Paolo Carlini <pcarlini at gmail dot com>, libstdc++ at gcc dot gnu dot org, Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Date: Wed, 05 Sep 2012 11:58:48 +0200
- Subject: Re: [v3] libstdc++/54296
- References: <503C9881.3080404@gmail.com> <CAH6eHdRBh41xaUWJaDQMGK1QReVXyA8q8qKRDKk9Lh6jZamDzg@mail.gmail.com> <503E7AFD.7090000@gmail.com> <CAP_SdMVgT0T0ZFLGpA6k72RnAN8jZDWT0ZfcjjTD9=np=dbHOA@mail.gmail.com> <CAH6eHdQ-L0P3=6ipp5KRJurw0ScKnFe616mdJSbdC2dG7VZhjw@mail.gmail.com> <503F2B93.2050801@gmail.com> <CAP_SdMW_=hSOVb0g_DV3jUdM3dbdXNTFiTu643huQiBDEWj80Q@mail.gmail.com> <50465FB2.803@gmail.com>
Hi,
On 09/04/2012 10:08 PM, François Dumont wrote:
On 08/30/2012 11:15 AM, Paolo Carlini wrote:
Hi,
> I simply don't want to pollute my system with experimental builds.
I have a gcc folder containing the image of gcc trunk and next to it
a gcc-build folder where the build takes place.
What about a gcc-install next to it? ;) This is what many people
have, me included, it's just matter of adding a --prefix to your
configure line, and you can install your compiler wherever you like.
But Jon can give you details, I already find this discussion a bit
surreal sorry ;)
Anyway, coming to the real work, I didn't have a chance to look into
the patch (this evening I will), for sure since you have an
"aborting" testcase ready, it should be Ok in terms of testing. I can
then take care of valgrind this time.
Paolo
Hi
I managed to do the test with Valgrind and so confirm the fix with
the attached patch (unmodified since last proposal).
Patch is Ok, thanks for your patience and thanks again for all your
great work on the unordered containers!
Paolo.