Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: bob_rossi@cox.net, gdb-patches@sources.redhat.com, nick@nick.uklinux.net
Subject: Re: [rfc] Annotation level THREE
Date: Wed, 12 Mar 2003 14:50:00 -0000	[thread overview]
Message-ID: <3E6F491A.4050401@redhat.com> (raw)
In-Reply-To: <200303120609.h2C69h904491@duracef.shout.net>

> Hi Andrew,
> 
> 
>> With this and its doco in, I think 5.4 is clear to go (or at least try to).
> 
> 
> The last time I looked in detail was 2003-02-16:
> 
>   http://sources.redhat.com/ml/gdb/2003-02/msg00257.html
> 
> At that time, there were still several high priority PR's about build
> issues; x86-64 regresions; and java fails the 'break main' test.
> 
> Do you care about any of these things?

`or at least try to'.  As far as I know this is the only feature that 
could block the next release.  It's critical that a GDB release 
containing this be made soon.

- x86-64 was always broken
- java improvements would be nice

A real concern is that `long long' regression.

Andrew



  reply	other threads:[~2003-03-12 14:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12  6:09 Michael Elizabeth Chastain
2003-03-12 14:50 ` Andrew Cagney [this message]
2003-03-12 14:56   ` Daniel Jacobowitz
2003-03-12 17:04   ` David Carlton
  -- strict thread matches above, loose matches on Subject: below --
2003-03-11 23:37 Andrew Cagney
2003-03-12 18:54 ` David Carlton
2003-03-12 19:04   ` Andrew Cagney
2003-03-14  0:08 ` Nick Roberts
2003-03-17  0:23   ` Andrew Cagney
2003-03-17 20:07     ` Nick Roberts
2003-03-17 20:38       ` Andrew Cagney
2003-03-18 10:31         ` Nick Roberts
2003-03-18 15:29           ` Andrew Cagney
2003-03-18 16:00           ` Andrew Cagney
2003-03-18 20:17             ` Bob Rossi

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=3E6F491A.4050401@redhat.com \
    --to=ac131313@redhat.com \
    --cc=bob_rossi@cox.net \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    --cc=nick@nick.uklinux.net \
    /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