From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, mec.gnu@mindspring.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Time for a HP/PA hackathon?
Date: Sat, 14 Feb 2004 20:00:00 -0000 [thread overview]
Message-ID: <20040214200010.B076E4B104@berman.michael-chastain.com> (raw)
> The 64-bit off_t, enabling the TUI, the HP/UX frame update, or the BFD
> file I/O rewrite?
The 64-bit off_t is the part that bothers me.
It's using a new host ABI that gdb hasn't used before, which means it's
likely to have problems on some hosts.
I don't feel as nervous about the TUI as you do. If it doesn't work on
some host, then we can just disable it on that host.
The HP/UX frame update doesn't bother me at all. We have a test suite.
I run it. It's covered, although the coverage is limited to HP's
compilers (no gcc) and HP-UX 11.11 (no 10.20 or 11.00).
I don't know anything about the BFD file I/O rewrite.
We aren't getting enough host-side coverage in gdb-testers. It's a
QA issue rather than a development issue. How does anyone know if the
new off_t code or the most recent readline code works on Cygwin or
AIX or Irix or Solaris?
> I do wonder if the next binutils branch should be held off until after
> GDB's been released - so that it can learn from GDB's mistakes :-)
It's easier for me if gdb doesn't branch until gcc 3.3.3 has released,
and a lot easier if binutils doesn't branch until gdb 6.1 has released
(preferably until after gdb gdb-6_1-branch has died).
Michael C
next reply other threads:[~2004-02-14 20:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 20:00 Michael Elizabeth Chastain [this message]
2004-02-15 1:20 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2004-02-14 3:14 Michael Elizabeth Chastain
2004-02-14 15:54 ` Andrew Cagney
2004-02-13 22:39 Michael Elizabeth Chastain
2004-02-14 2:01 ` Andrew Cagney
2004-02-13 18:13 Michael Elizabeth Chastain
2004-02-13 18:32 ` Elena Zannoni
2004-02-13 18:48 ` Andrew Cagney
2004-02-13 16:29 Michael Elizabeth Chastain
2004-02-13 16:54 ` Andrew Cagney
2004-02-11 17:05 Andrew Cagney
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=20040214200010.B076E4B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/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