From: Mark Mitchell <mark@codesourcery.com>
To: "Nitin Gupta, Noida" <niting@noida.hcltech.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: RE: libstdc++ support for H8300-elf in gcc 3.1.1
Date: Mon, 29 Jul 2002 17:53:00 -0000 [thread overview]
Message-ID: <13010000.1027956984@warlock.codesourcery.com> (raw)
In-Reply-To: <E04CF3F88ACBD5119EFE00508BBB212103B7E66E@exch-01.noida.hcltech.com>
--On Monday, July 29, 2002 08:28:51 PM +0530 "Nitin Gupta, Noida"
<niting@noida.hcltech.com> wrote:
> Hi,
> I'm confused! I don't see this patch checked in gcc sources
> in the described version number of the gcc/configure.in
>
> http://sources.redhat.com/ml/gdb-patches/2001-09/msg00001.html
>
> It is not present in gcc 3.1.1 however it is there in sources
> downloded from cvs head (3.3) @subversions.gnu.org:/cvsroot/gcc.
> Can this patch be released with 3.2 also?
No; 3.2 is an ABI bug-fix only release.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-07-29 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 11:45 Nitin Gupta, Noida
2002-07-29 17:53 ` Mark Mitchell [this message]
[not found] <E04CF3F88ACBD5119EFE00508BBB212103AEC423@exch-01.noida.hcltech. com>
2002-07-27 16:15 ` Nitin Gupta, Noida
2002-07-29 4:42 ` Mark Mitchell
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=13010000.1027956984@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=niting@noida.hcltech.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).