From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb-patches@sourceware.org
Subject: Re: ping: [patch 1/2] Fix gdb.cp/gdb2495.exp regression with gcc-4.7 #5
Date: Mon, 11 Jun 2012 19:25:00 -0000 [thread overview]
Message-ID: <20120611192459.GM2687@adacore.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2012-06-11 19:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 21:01 Jan Kratochvil
2012-03-26 19:04 ` ping: " Jan Kratochvil
2012-03-26 19:53 ` Mark Kettenis
2012-03-26 20:32 ` Jan Kratochvil
2012-03-26 21:45 ` Mark Kettenis
2012-03-27 8:15 ` Jan Kratochvil
2012-06-11 15:22 ` Joel Brobecker
2012-06-11 16:09 ` Jan Kratochvil
2012-06-11 19:25 ` Joel Brobecker [this message]
2012-06-11 19:41 ` Jan Kratochvil
2012-06-11 19:51 ` Jan Kratochvil
2012-06-13 15:01 ` Joel Brobecker
2012-06-13 15:03 ` Jan Kratochvil
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=20120611192459.GM2687@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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: link
Be 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