public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: danglin@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/6483: ada fails to build under hppa*-hp-hpux*
Date: Tue, 30 Apr 2002 10:36:00 -0000	[thread overview]
Message-ID: <20020430173602.1946.qmail@sources.redhat.com> (raw)

The following reply was made to PR ada/6483; it has been noted by GNATS.

From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: mark@codesourcery.com (Mark Mitchell)
Cc: fw@deneb.enyo.de, dave.anglin@nrc.ca, gcc-gnats@gcc.gnu.org,
   zack@codesourcery.com
Subject: Re: ada/6483: ada fails to build under hppa*-hp-hpux*
Date: Tue, 30 Apr 2002 13:32:15 -0400 (EDT)

 > > Then, I don't understand the FSF point of view on what's a regression.
 > 
 > It's not a regression because we never had a release where this worked.
 
 OK, I see.  ADA wasn't integrated into the GCC tree before.  However,
 the makefile infrastructure existed which enabled you to build ada if it
 was inserted into the tree.
 
 Possibly the other high priority ada PRs should not be marked as high
 priority.
 
 In looking at <http://gcc.gnu.org/gcc-3.1/changes.html>, there is no
 mention that ADA is new.
 
 Dave
 -- 
 J. David Anglin                                  dave.anglin@nrc.ca
 National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)


             reply	other threads:[~2002-04-30 17:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-30 10:36 John David Anglin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-30 14:56 Mark Mitchell
2002-04-30 14:56 zack
2002-04-30 14:56 John David Anglin
2002-04-30 12:21 danglin
2002-04-30 11:26 Mark Mitchell
2002-04-30 11:16 John David Anglin
2002-04-30 11:06 zack
2002-04-30 10:46 John David Anglin
2002-04-30 10:26 Mark Mitchell
2002-04-30  8:36 Florian Weimer
2002-04-26 16:50 danglin
2002-04-26 16:46 dave.anglin

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=20020430173602.1946.qmail@sources.redhat.com \
    --to=dave@hiauly1.hia.nrc.ca \
    --cc=danglin@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    /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).