This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/70360] --enable-vtable-verify
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 23 Mar 2016 01:37:38 +0000
- Subject: [Bug libstdc++/70360] --enable-vtable-verify
- Auto-submitted: auto-generated
- References: <bug-70360-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70360
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to psturm from comment #3)
> I understand the test suite cannot contemplate every single combination of
> configure options. However, I would suggest that certain combinations might
> be more common than others.
That certainly doesn't apply to VTV, I don't know of anybody using it.
> I am not a programmer, but I can run the builds with various build
> parameters and report my results. Most of the 2106 failures for libstdc++
> are for "compilation failed to produce executable", so I suspect if we can
> figure out why that is happening, we can dramatically reduce the scope of
> what we need to look at.
Looks in $target/libstdc++-v3/testsuite/libstdc++.log