This is the mail archive of the binutils@sourceware.org mailing list for the binutils 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: Supporting more than one CPU with the same gas port.

From: nick clifton <nickc at redhat dot com>
To: Fred Cooke <fred dot cooke at gmail dot com>
Cc: binutils at sourceware dot org, James Murray <jsm at jsm-net dot demon dot co dot uk>
Date: Thu, 05 Jan 2012 11:03:24 +0000
Subject: Re: Supporting more than one CPU with the same gas port.
References: <4F0379F1.6030901@ipdatasys.com> <4F043066.2060603@redhat.com> <1325684110.2430.314.camel@jsm2> <CABZhLO_yM_k80iKbBrUzRYVTWmbjypO0qSTR2VjKbkmEYVjVqQ@mail.gmail.com>

Hi Fred

Nick, would you say that it is in bad taste to try to make one
assembler handle two different sets of opcodes in one table, two
different sets of registers in one struct, etc? I would.

Bad taste - no. A magnet for bugs - yes.

Mind you, I suspect that this sort of thing (a computing device with more than one type of CPU sharing the memory and other resources) might become more prevalent in the future. If it does, then the binutils will need to adapt to be able to handle generating executables for such devices.

Cheers
  Nick

Follow-Ups:
- Re: Supporting more than one CPU with the same gas port.
  - From: Joseph S. Myers

References:
- Supporting more than one CPU with the same gas port.
  - From: Sean Keys
- Re: Supporting more than one CPU with the same gas port.
  - From: nick clifton
- Re: Supporting more than one CPU with the same gas port.
  - From: James Murray
- Re: Supporting more than one CPU with the same gas port.
  - From: Fred Cooke

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