From: Ian Lance Taylor Date: Fri, 28 Jun 1996 16:38:05 +0000 (+0000) Subject: various trivial cleanups X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=77dea5447d27240266be1b2391dcd774b90a181a;p=binutils-gdb.git various trivial cleanups --- diff --git a/gas/.Sanitize b/gas/.Sanitize index 17cc3e9641e..4df4e45c6c3 100644 --- a/gas/.Sanitize +++ b/gas/.Sanitize @@ -32,10 +32,7 @@ NEWS NOTES NOTES.config README -README-quirks README-vms -README.coff -README.rich acconfig.h aclocal.m4 app.c diff --git a/gas/ChangeLog b/gas/ChangeLog index 3e92aae21bc..b0dc1149c6b 100644 --- a/gas/ChangeLog +++ b/gas/ChangeLog @@ -1487,7 +1487,6 @@ Mon Dec 11 16:23:51 1995 Stan Shebs * mac-as.r: Fix copyright and version strings. (cfrg): Use PROG_NAME instead of literal name. - Mon Dec 11 14:14:08 1995 Ian Lance Taylor * read.c (read_a_source_file): If tc_unrecognized_line is defined, diff --git a/gas/NOTES b/gas/NOTES index b062909db12..18b29b81914 100644 --- a/gas/NOTES +++ b/gas/NOTES @@ -5,23 +5,16 @@ PORTING: Sorry, no description of the interfaces is written up yet. Look at existing back ends and work from there. -New hosts: If your host system has a strange header file setup, create a -config/ho-foo.h file for it and include the appropriate header files or -definitions there. If your host has a broken compiler, or some broken macros -in header files, create a host-specific file and repair the damage there. -(See, for example, ho-rs6000.h. The "assert" macro on that system doesn't work -right, and a flag is set to rewrite an expression in tc-m68k.c that the native -compiler mis-compiles.) - -New target formats: Look at the BFD_ASSEMBLER code. The a.out code might be a -fair example. There are no "good" examples yet, unfortunately, nor any good -documentation of the changes. +New hosts: The configure script, which is generated by autoconf, +should handle all host specific configuration. + +New target formats: Look at the BFD_ASSEMBLER code. The a.out or ELF +code might be a fair example. There are no "good" examples yet, +unfortunately, nor any good documentation of the changes. New target processors: Check first to see if the BFD_ASSEMBLER interface is supported by the file format code you need to use. -New environments: ??? - DOCUMENTATION: The internals of gas need documenting. @@ -45,10 +38,6 @@ non-BFD_ASSEMBLER version often has multiple conditional tests inside it for various processors or formats. As the various targets get converted over, these will gradually go away. -As of the moment I'm editing this file, only the "sun4" and "decstation-bsd" -targets can really use the BFD code. Other back ends still need merging or -touching up. - TO DO: Remove DONTDEF code, commented-out code. @@ -105,30 +94,6 @@ Torbjorn Granlund writes, regarding alpha .align: since these two instructions can dual-issue. Since .align is ued a lot by gcc, it is an important optimization. -Torbjorn Granlund writes, regarding i386/i486/pentium: - - In a new publication from Intel, "Optimization for Intel's 32 bit - Processors", they recommended code alignment on a 16 byte boundary if that - requires less than 8 bytes of fill instructions. The Pentium is not - affected by such alignment, the 386 wants alignment on a 4 byte boundary. - It is the 486 that is most helped by large alignment. - - Recommended nop instructions: - 1 byte: 90 xchg %eax,%eax - 2 bytes: 8b c0 movl %eax,%eax - 3 bytes: 8d 76 00 leal 0(%esi),%esi - 4 bytes: 8d 74 26 00 leal 0(%esi),%esi - 5 bytes: 8b c0 8d 76 00 movl %eax,%eax; leal 0(%esi),%esi - 6 bytes: 8d b6 00 00 00 00 leal 0(%esi),%esi - 7 bytes: 8d b4 26 00 00 00 00 leal 0(%esi),%esi - - Note that `leal 0(%esi),%esi' has a few different encodings... - - There are faster instructions for certain lengths, that are not true nops. - If you can determine that a register and the condition code is dead (by - scanning forwards for a register that is written before it is read, and - similar for cc) you can use a `incl reg' for a 3 times faster 1 cycle nop... - (From old "NOTES" file to-do list, not really reviewed:) fix relocation types for i860, perhaps by adding a ref pointer to fixS? diff --git a/gas/NOTES.config b/gas/NOTES.config index e12797d51c1..79832e64d7a 100644 --- a/gas/NOTES.config +++ b/gas/NOTES.config @@ -3,30 +3,20 @@ Theory: -The goal of the new configuration scheme is to bury all object format, -target processor, and host machine dependancies in object, target, and -host specific files. That is, to move all #ifdef's out of the gas -common code. +The goal of the new configuration scheme is to bury all object format +and target processor dependancies in object and target specific files. +That is, to move all #ifdef's out of the gas common code. Here's how it works. There is a .h and a .c file for each object file -format, a .h and a .c file for each target processor, and a .h for -each host. config.gas creates {sym}links in the current directory to -the appropriate files in the config directory. config.gas also serves -as a list of triplets {host, target, object-format} that have been -tested at one time or another. I also recommend that config.gas be -used to document triplet specific notes as to purpose of the triplet, -etc. +format and a .h and a .c file for each target processor. The +configure script creates symlinks in the current directory to the +appropriate files in the config directory. configure also serves as a +list of triplets {host, target, object-format} that have been tested +at one time or another. I also recommend that configure be used to +document triplet specific notes as to purpose of the triplet, etc. Implementation: -host.h is a {sym}link to .../config/xm-yourhost.h. It is intended to -be used to hide host compiler, system header file, and system library -differences between host machines. If your host needs actual c source -files, then either: these are generally useful functions, in which -case you should probably build a local library outside of the gas -source tree, or someone, perhaps me, is confused about what is needed -by different hosts. - obj-format.h is a {sym}link to .../config/obj-something.h. It is intended All gas .c files include as.h. diff --git a/gas/README-quirks b/gas/README-quirks deleted file mode 100644 index c9a3b05917a..00000000000 --- a/gas/README-quirks +++ /dev/null @@ -1,7 +0,0 @@ -* rcsid's should be conspicuously absent until someone explains to me - how to use them constructively without affecting diffs from remote - sites. If you can, then I will become an active supporter of - rcsid's. - -* "diff -u" patches preferred. "diff -c" patches accepted. All other - patches will be returned. diff --git a/gas/README.coff b/gas/README.coff deleted file mode 100644 index 46c61cda909..00000000000 --- a/gas/README.coff +++ /dev/null @@ -1,79 +0,0 @@ -The coff patches intend to do the following : - - . Generate coff files very compatible with vanilla linker. - . Understands coff debug directives. - -Here are the guidelines of the work I have done : - - . Encapsulate format dependent code in macros where it is possible. - . Where not possible differenciate with #ifdef - . try not to change the calling conventions of the existing functions. - I made one exception : symbol_new. I would be pleased to hear about - a better solution. (symbols.c) - . Extend the use of N_TYPE_seg seg_N_TYPE tables so that segments can - be manipulated without using their format dependent name. (subsegs.c) - . Write a function to parse the .def debug directives - . Write two small peaces of code to handle the .ln directive. - . In write.c try to move all the cross compilation specifics (md_..) to - format dependent files. - . Encapsulate the data structures using generic types, macros calls. - . Added too much code to resolve the complexity of the symbol table - generated. Most of the code deals with debug stuff. - . Create another makefile, shorter, cleaner. - . Create a config.gas shell script to mimic the gcc,gdb... configuration - mechanism. This reduce the complexity of the makefile. - . Isolate the format dependent code in two files - coff.c coff.h - aout.c aout.h - elf.c elf.h [ Not yet ;-] - . added a little stack management routine for coff in file stack.c - . isolate os specific flags in m- files - -If further development is planed on it is should solve the following problems : - - . Encapsulate DESC & OTHER tests in a macro call. I'm not aware - of their exact semantics. - . Clean up the seg_N_TYPE N_TYPE_seg naming scheme - . Try to remove as much reference to segment dependent names as possible - . Find a cleaner solution for symbol_new. - . Report the modifications on vax, ns32k, sparc machine dependent files. - To acheive this goal, search for \