sh_flags vs bfd

[Richard Henderson <rth at redhat dot com>]

I have need to get a processor specific bit set in sh_flags.  At
present there is no way to smuggle those bits from the assembler
through to the elf bfd backend.

Since we're almost out of bits in "flags", I thought about adding
new fields to struct sec, but chickened out since I only need a
single bit at the moment.



r~


        * section.c (SEC_ARCH_BIT_0): New; replace unused SEC_BALIGN.
        * bfd-in2.h: Rebuild.

Index: section.c
===================================================================
RCS file: /cvs/src/src/bfd/section.c,v
retrieving revision 1.34
diff -c -p -d -r1.34 section.c
*** section.c	2001/09/18 09:57:26	1.34
--- section.c	2001/09/28 20:49:53
*************** CODE_FRAGMENT
*** 205,213 ****
  .     some relocation information too.  *}
  .#define SEC_RELOC      0x004
  .
! .#if 0   {* Obsolete ? *}
! .#define SEC_BALIGN     0x008
! .#endif
  .
  .  {* A signal to the OS that the section contains read only data.  *}
  .#define SEC_READONLY   0x010
--- 205,215 ----
  .     some relocation information too.  *}
  .#define SEC_RELOC      0x004
  .
! .  {* ELF reserves 4 processor specific bits and 8 operating system
! .     specific bits in sh_flags; at present we can get away with just
! .     one in communicating between the assembler and BFD, but this
! .     isn't a good long-term solution.  *}
! .#define SEC_ARCH_BIT_0 0x008
  .
  .  {* A signal to the OS that the section contains read only data.  *}
  .#define SEC_READONLY   0x010