public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nick Burrett <nick.burrett@btinternet.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Target deprecation, round three
Date: Mon, 24 Feb 2003 22:40:00 -0000	[thread overview]
Message-ID: <3E5A9499.1070502@btinternet.com> (raw)
In-Reply-To: <87r89y9qm8.fsf@egil.codesourcery.com>

Zack Weinberg wrote:

> The majority of the targets on my "round two" list
> (http://gcc.gnu.org/ml/gcc/2002-12/msg00702.html) went over without
> comment.  With a couple of exceptions I've dropped the targets which
> someone spoke up in favor of; let's discuss the exceptions a bit more
> carefully.  (If your favorite target is still on the list, speak up!
> If you did already, it means I lost your mail; my apologies, and
> please remind me.)
> 
> I'm pushing back on the following:

> 	arm*-*-aof*
> 
>   This target is responsible for masses of #ifdefs all over the ARM
>   back end.  Is it *really* necessary to continue using this rather
>   quirky assembler?  Could you perhaps move to GAS and arm-elf
>   instead?

Unfortunately this is not possible, though I've considered switching to 
GAS and arm-elf in the past.  RISC OS does not support ELF binaries.

However the rest of the code and patches to support RISC OS are kept in 
my own private tree, so it is feasible for me to just move the AOF stuff 
into my own set of patches.

It would be handy if you could leave it in for 3.3, then dump it for 3.4 
and later releases if you like.

Cheers,


Nick.

  parent reply	other threads:[~2003-02-24 21:50 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24  6:58 Zack Weinberg
2003-02-24 12:43 ` Hans-Peter Nilsson
2003-02-24 17:32   ` Zack Weinberg
2003-02-24 17:47     ` Hans-Peter Nilsson
2003-02-24 17:48       ` Zack Weinberg
2003-02-24 18:10         ` Hans-Peter Nilsson
2003-02-24 14:47 ` Daniel Jacobowitz
2003-02-24 16:13 ` arc-*-* was " Joel Sherrill
2003-02-24 17:32   ` Zack Weinberg
2003-02-24 17:46     ` Joel Sherrill
2003-02-24 16:17 ` David Edelsohn
2003-02-24 16:45   ` Andreas Jaeger
2003-02-24 16:46     ` David Edelsohn
2003-02-24 17:20   ` Zack Weinberg
2003-02-24 18:27     ` David Edelsohn
2003-02-24 18:37       ` Zack Weinberg
2003-02-24 19:36         ` Gabriel Dos Reis
2003-02-24 19:49           ` Zack Weinberg
2003-02-24 19:56             ` Gabriel Dos Reis
2003-02-24 20:02             ` David Edelsohn
2003-02-24 20:13               ` Gabriel Dos Reis
2003-02-24 21:14               ` Zack Weinberg
2003-02-24 21:42                 ` David Edelsohn
2003-02-24 23:03                   ` Mark Mitchell
2003-02-24 23:07                     ` Daniel Jacobowitz
2003-02-24 23:15                       ` David Edelsohn
2003-02-24 23:40                         ` Steven Bosscher
2003-02-25  1:44                           ` David Edelsohn
2003-02-25  6:45                             ` Tolga Dalman
2003-02-26  0:06                         ` Richard Henderson
2003-02-24 23:08                     ` David Edelsohn
2003-02-24 23:29                     ` Zack Weinberg
2003-02-25  3:26                 ` Fergus Henderson
2003-04-14 16:57                   ` Nick Ing-Simmons
2003-02-24 18:44 ` DJ Delorie
2003-02-24 18:57   ` Zack Weinberg
2003-02-24 21:49 ` Franz Sirl
2003-02-24 22:40 ` Nick Burrett [this message]
2003-02-24 22:47 ` Andreas Schwab
2003-02-25 11:14 ` Ralf Corsepius
2003-02-25 14:57   ` Joel Sherrill
2003-02-25 15:33     ` Ralf Corsepius
2003-02-25 15:36       ` Joel Sherrill
2003-02-25 19:23         ` Zack Weinberg
2003-02-25 19:25           ` Joel Sherrill
2003-02-25 19:28           ` Joel Sherrill
2003-02-25 20:36             ` Zack Weinberg
2003-02-25 23:55 ` Richard Henderson
2003-02-25  9:15 Nathanael Nerode
2003-02-25 17:59 ` David Edelsohn
2003-02-25 18:16   ` Nathanael Nerode
2003-02-25 16:57 Chris Lattner

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=3E5A9499.1070502@btinternet.com \
    --to=nick.burrett@btinternet.com \
    --cc=gcc@gcc.gnu.org \
    --cc=zack@codesourcery.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).