This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Helping out GDB
- To: jdein at windriver dot com, martin at loewis dot home dot cs dot tu-berlin dot de
- Subject: Re: Helping out GDB
- From: "James L. Dein" <jdein at windriver dot com>
- Date: Mon, 17 Jul 2000 19:02:52 -0700 (PDT)
- Cc: dberlin at redhat dot com, dje at watson dot ibm dot com, gcc at gcc dot gnu dot org
> From gcc-return-18993-jdein=wrs.com@gcc.gnu.org Fri Jul 14 16:05 PDT 2000
> Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
> List-Unsubscribe: <mailto:gcc-unsubscribe-jdein=wrs.com@gcc.gnu.org>
> List-Archive: <http://gcc.gnu.org/ml/gcc/>
> List-Post: <mailto:gcc@gcc.gnu.org>
> List-Help: <http://egcs.cygnus.com/ml/>
> Delivered-To: mailing list gcc@gcc.gnu.org
> Date: Sat, 15 Jul 2000 01:04:23 +0200
> From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
> To: jdein@windriver.com
> CC: dberlin@redhat.com, dje@watson.ibm.com, gcc@gcc.gnu.org
> Subject: Re: Helping out GDB
> User-Agent: SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) Emacs/20.4
(i586-pc-linux-gnu) MULE/4.0 (HANANOEN)
> MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko")
>
> > VxWorks requires 'gcc2_compiled.'. When gcc3_compiled. comes out,
> > it will need that too.
>
> Could you please be a bit more specific what it needs that for? I
> thought about proposing a patch to remove this feature entirely. If it
> is to stay, I think its applications will need to be documented, so
> future maintainers can re-validate the rationale for having it.
Oh, well. Your request-for-info has led to a furious :-) disucussion here, and
it appears that `gcc2_compiled.' will not be an issue after all. Feel free to
nuke it. Sorry about the red herring.
Our downloading tools sometimes use gcc_compiled. to identify the code as being
built with GNU (rather than a proprietary compiler).
Jim Dein
> Regards,
> Martin
>