This is the mail archive of the mailing list for the gas2 project.

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

Re: other apps that assemble code

   Date: Thu, 5 Feb 1998 12:49:11 -0600 (CST)
   From: Joel Sherrill <>

   >    Date: Thu, 5 Feb 1998 11:47:36 -0600 (CST)
   >    From: Joel Sherrill <>
   >    I have seen articles about "optimizing assemblers" for really smart cpus
   >    which insert nops, reorder instructions to avoid stalls, reassign
   >    registers, etc.   This type of tools would benefit from a generic assembly
   >    language parser.
   > Ok, but methinks this is still just GAS.
   > Or am I misunderstanding something?

   I guess it could be but would it be cleaner to have it as a separate tool
   which manipulated source.  Technically either approach is viable.

   >From an implementation standpoint, having a separate tool might make that
   tool easier to update/port.  From a strict viewpoint, gas shoud only take
   assembler and generate object.  That is a difficult enough process as it
   is.  Having to deal with possible code reordering, nops could only make
   gas more complex and difficult to maintain.

   I don't know much about gas internals.  Does it have an internal
   representation which could be manipulated like this?

Nope (or rather, yep for some particular ports for some limited forms of