public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb@sources.redhat.com
Subject: Re: [HEADS UP] Merging i386newframe into mailine
Date: Fri, 23 May 2003 17:15:00 -0000	[thread overview]
Message-ID: <3ECE5728.5040306@redhat.com> (raw)
In-Reply-To: <200305231652.h4NGqs4Y023667@elgar.kettenis.dyndns.org>

> Folks,
> 
> Now that Elena en Michal have tested my i386newframe branch on amd64,
> and found it to be in a much better state than mainline, I think I can
> seriously consider bringing the new stuff over to mainline.
> 
> This will give us:
> 
> * Improvements to the prologue analyzer.
> * Support for DWARF CFI on i386.
> 
> At the cost of:
> 
> * Possibly breaking a few unmaintained i386 targets.
> * Possibly introducing bugs due to the DWARF CFI code.
> * Possibly exposing bugs lurking in the new frame unwinder code.
> 
> This might lead to a delay in the GDB 6 release, or might force us to
> make a bugfix release pretty soon after the initial 6.0 release.

Ah, such is life :-)

> I think it's worth running these risks, especially since recent
> devlopments on Linux/i386 demand DWARF CFI support on the i386.
> Therefore I'll do the merge from next Thursday onwards, unless someone
> objects.

It's all marketing :-)

Only the ``early adaptors'' are likely to try a new even release.  The 
more serious users anticipating either 6.0.1 or 6.1.

:-^

Andrew


  reply	other threads:[~2003-05-23 17:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23 16:52 Mark Kettenis
2003-05-23 17:15 ` Andrew Cagney [this message]
2003-05-24  9:52 ` Eli Zaretskii
2003-05-24 11:27   ` Mark Kettenis
2003-05-24 17:38     ` Eli Zaretskii
2003-05-26 15:31   ` Andrew Cagney
2003-05-29 15:14     ` Mark Kettenis
2003-05-29 16:48       ` Andrew Cagney
     [not found] ` <200305231745.h4NHj2JL029521@gremlin.ics.uci.edu>
2003-05-24 11:15   ` Mark Kettenis

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=3ECE5728.5040306@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=kettenis@chello.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).