This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: ping: [patch 1/2] Fix gdb.cp/gdb2495.exp regression with gcc-4.7 #5
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: Mark Kettenis <mark dot kettenis at xs4all dot nl>, gdb-patches at sourceware dot org
- Date: Mon, 11 Jun 2012 12:24:59 -0700
- Subject: Re: ping: [patch 1/2] Fix gdb.cp/gdb2495.exp regression with gcc-4.7 #5
- References: <20120309210045.GA30432@host2.jankratochvil.net> <20120326190355.GA11001@host2.jankratochvil.net> <201203261953.q2QJrXX4023325@glazunov.sibelius.xs4all.nl> <20120326203151.GA18085@host2.jankratochvil.net> <201203262145.q2QLjRIJ024024@glazunov.sibelius.xs4all.nl> <20120327081439.GA8387@host2.jankratochvil.net> <20120611152148.GA31854@adacore.com> <20120611160830.GA10865@host2.jankratochvil.net>
> I am not sure what to do with it. I think it is definitely needed as without
> this patch gdb.cp/gdb2495.exp regresses which is user visiable.
>
> But it introduces the regression exploited by the testcase below.
:-(. I am not sure what to do either. Do you think we could have
a solution in a reasonable amount of time? I don't want to give up
to easily, but it feels like the further we go, the more issue we
find (it feels the same way I felt with the objfile search order
patch series).
We have several options:
1. Ignore the initial regression, and release with it
2. Revert the patch that caused the regression. I can't remember
which patch that was, and whether it would "unsolve" an important
issue.
3. Ignore the side-effect/regression caused by this fix, and fix
it later
4. Delay the release in order to implement setjmp handling.
Not being completely up to speed with the issues involved, I am
not sure which one would make sense. Delaying the release would
have some impact on Maciej's mips work, but is otherwise a real
possibility.
--
Joel