public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: gcc 2 survey
Date: Fri, 19 Sep 2003 23:57:00 -0000	[thread overview]
Message-ID: <20030919235727.GB17343@redhat.com> (raw)
In-Reply-To: <200309192210.h8JMAltE021584@duracef.shout.net>

On Fri, Sep 19, 2003 at 06:10:47PM -0400, Michael Elizabeth Chastain wrote:
>gcc 2 survey
>2003-09-19
>mec@shout.net
>
>Here is a bunch of data that I researched on platforms that still
>use gcc 2.
>
>At this time I am continuing to test with gcc 2.95.3, and I recommend that
>we keep fixing any gdb regressions that happen with gcc 2.95.3.
>
>Michael C
>
>. Three-line summary
>
>  gcc 2: openbsd, netbsd, freebsd, debian, lindows, xandros, lycoris, apple, sco
>  gcc 3: red hat, mandrake, suse, slackware, conectiva, knoppix, gentoo
>  gcc 3: hurd, cygwin

Cygwin falls into this list, too.  It has a separate gcc2 package.

cgf

  reply	other threads:[~2003-09-19 23:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19 22:10 Michael Elizabeth Chastain
2003-09-19 23:57 ` Christopher Faylor [this message]
2003-09-22 22:21 ` Jason Molenda

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=20030919235727.GB17343@redhat.com \
    --to=cgf@redhat.com \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).