From: Richard Henderson <rth@redhat.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Patch: remove some junk left behind from obsolete targets
Date: Tue, 13 Aug 2002 19:49:00 -0000 [thread overview]
Message-ID: <20020813194848.F23595@redhat.com> (raw)
In-Reply-To: <200208132245.SAA01497@caip.rutgers.edu>; from ghazi@caip.rutgers.edu on Tue, Aug 13, 2002 at 06:45:23PM -0400
On Tue, Aug 13, 2002 at 06:45:23PM -0400, Kaveh R. Ghazi wrote:
> * m68k.c (m68k_output_function_prologue,
> m68k_output_function_epilogue): Delete versions for DPX2/MOTOROLA
> and NEWS/MOTOROLA.
> * genattrtab.c: Remove dpx2 comment.
> * libgcc2.c (__enable_execute_stack): Delete versions for
> NeXT/__MACH__, __convex__, __sysV88__, __pyr__ and
> sony_news/SYSTYPE_BSD.
> * longlong.h: Delete code for __a29k__, _AM29K, __clipper__,
> __gmicro__, __i860__, __NeXT__ and __pyr__.
> * rtl.h: Remove convex comment.
> * varasm.c: Likewise.
Ok.
r~
prev parent reply other threads:[~2002-08-14 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 15:45 Kaveh R. Ghazi
2002-08-13 19:49 ` Richard Henderson [this message]
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=20020813194848.F23595@redhat.com \
--to=rth@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
/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).