From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: [Archer] Re: [Archer] C++ draft
Date: Wed, 29 Jun 2011 21:47:00 -0000 [thread overview]
Message-ID: <20110629214656.GN2421@adacore.com> (raw)
In-Reply-To: <m37h84xvj0.fsf@fleche.redhat.com>
> I definitely wouldn't put it that way. If you ship on hosts where this
> is a problem, it is best to confront it in advance.
>
> Could you say what hosts you are worried about?
Right now, I'm mostly worried about AIX, and HP/UX. Our last Tru64
machine died of a sudden death, so I can't help with that port
anymore. I also need to think about Windows x64, but we already
have a C++ compiler on 32bit Windows, so I'm hoping it'll be easy
enough to build a 64bit version.
But really, I am just going to have to convince the guys at AdaCore
that I just need these compilers, and pronto :-).
> Actually, debugging GDB will improve. Hard to believe, but I think it
> is true.
OK, you've seem to have thought through this quite a bit, so
I look forward to seeing those improvements...
--
Joel
next prev parent reply other threads:[~2011-06-29 21:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 21:08 Tom Tromey
2011-06-27 21:23 ` [Archer] " Joel Brobecker
2011-06-29 19:55 ` Tom Tromey
2011-06-29 21:47 ` Joel Brobecker [this message]
2011-06-28 4:33 ` Matt Rice
2011-06-28 8:21 ` Yao Qi
2011-06-28 12:21 ` Gary Benson
2011-06-28 17:08 ` Matt Rice
2011-06-28 17:36 ` Jan Kratochvil
2011-06-29 20:08 ` Tom Tromey
2011-06-29 20:06 ` Tom Tromey
2011-06-30 6:06 ` Yao Qi
2011-09-26 21:01 ` Jim Blandy
2011-06-29 18:52 ` Stan Shebs
2011-06-29 19:03 ` [Archer] " Joel Brobecker
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=20110629214656.GN2421@adacore.com \
--to=brobecker@adacore.com \
--cc=archer@sourceware.org \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).