Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Wed, 13 Jun 2012 15:01:00 -0000	[thread overview]
Message-ID: <20120613150044.GF18729@adacore.com> (raw)
In-Reply-To: <20120611194037.GA32003@host2.jankratochvil.net>

I took some time to sleep on this...

> >   1. Ignore the initial regression, and release with it
> 
> This is not good, this regresses a nice C++ fixup by Tom.
> 
> 
> >   2. Revert the patch that caused the regression. I can't remember
> >      which patch that was, and whether it would "unsolve" an important
> >      issue.
> 
> The regression is due to binutils fix by Jakub Jelinek:
> 	http://sourceware.org/bugzilla/show_bug.cgi?id=12570
> 
> There is nothing to revert.  The original assumption _start has no unwind info
> was just wrong.  Moreover there was a bug that it relied upon the fact that
> .plt has no unwind info.  But after fixing it to make it really _start (and
> not .plt) some archs (ppc IIRC) has unwind info even for _start.

OK and OK. Thanks for the feedback on these points.

> >   3. Ignore the side-effect/regression caused by this fix, and fix
> >      it later
> 
> Yes, I find it a viable alternative.
> 
> 
> >   4. Delay the release in order to implement setjmp handling.
> 
> I already tried to implement it once but somehow did not finish it.  I do no
> like much that even the longjmps tracking is not a perfect solution.

It seems to me that fixing the problem is going to be quite delicate,
since you keep finding regressions with all the solutions you've been
considering. So I am inclined to accept the regression for 7.5 too.

-- 
Joel


  parent reply	other threads:[~2012-06-13 15:01 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
2012-06-11 19:41                 ` Jan Kratochvil
2012-06-11 19:51                   ` Jan Kratochvil
2012-06-13 15:01                   ` Joel Brobecker [this message]
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=20120613150044.GF18729@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