This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: m68k target deprecations

From: Joel Sherrill <joel dot sherrill at OARcorp dot com>
To: Joe Buck <jbuck at synopsys dot com>
Cc: Don Lindsay <lindsayd at cisco dot com>, Bernardo Innocenti <bernie at develer dot com>, gcc at gcc dot gnu dot org, Richard Henderson <rth at redhat dot com>, Andreas Schwab <schwab at suse dot de>,Gunther Nikl <gni at gecko dot de>
Date: Fri, 12 Sep 2003 15:21:09 -0500
Subject: Re: m68k target deprecations
Organization: OAR Corporation
References: <3F60EC0A.8060900@develer.com> <Pine.LNX.4.44.0309121150550.12317-100000@dlindsay-lnx.cisco.com> <20030912122424.A14202@synopsys.com>

Joe Buck wrote:

On Fri, Sep 12, 2003 at 11:55:10AM -0700, Don Lindsay wrote:

Cisco still uses m68k-aout.

For new development? Or are they just shipping an old product that uses aout?


And if for new development, is it possible to switch
to m68k-elf and use objcopy to produce the final
image for the target hardware.

In the RTEMS world, we make a strong distinction
between the object format used to link and debug
with and the format required by the target hardware
loader.

--joel

Follow-Ups:
- Re: m68k target deprecations
  - From: Gunther Nikl

References:
- m68k target deprecations
  - From: Bernardo Innocenti
- Re: m68k target deprecations
  - From: Don Lindsay
- Re: m68k target deprecations
  - From: Joe Buck

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]