Re: Please send in binutils patches

[Manfred Hollstein <manfred@s.direktnet.de>]

On Wed, 4 February 1998, 17:10:59, ian@cygnus.com wrote:

 > I would like to start making the binutils 2.9 release.
 > 
 > If you have any patches that you would like to get into the release,
 > please send them to me.
 > 
 > I have gone through my list of submitted patches.  If you have sent me
 > a patch, and you haven't heard anything back, then I lost it (except,
 > H.J., I haven't dealt with the libtool library version name stuff
 > yet).

I  just  checked     gas-980210  on    `sparc-sun-solaris2.5.1'    and
`sparc-sun-sunos4.1.4' without problems!

But on    m88k-motorola-sysv3  I  wasn't  able  to    compile the  new
`gas/ehopt.c' without my appended patch. The next machine in the queue
then is the slowest one: m68k-motorola-sysv; but as  it uses COFF like
the m88k I don't expect any more problems.

Thu Feb 12 07:56:08 1998  Manfred Hollstein  <manfred@s-direktnet.de>

	* ehopt.c (eh_frame_code_alignment): If not BFD_ASSEMBLER, set fix based
	on segment_info[now_seg] resp. {text,data,bss}_fix_root.

diff --context --recursive --show-c-function -x *.o -x *.info* -x *.html* -x *.elc -x *.dvi -x *.orig -x *~ -x version.el gas-980210.orig/gas/ehopt.c gas-980210/gas/ehopt.c
*** gas-980210.orig/gas/ehopt.c	Tue Feb 10 19:55:13 1998
--- gas-980210/gas/ehopt.c	Thu Feb 12 07:57:12 1998
*************** eh_frame_code_alignment ()
*** 109,115 ****
--- 109,135 ----
    current_subseg = now_subseg;
    subseg_new (".eh_frame", 0);
    f = seg_info (now_seg)->frchainP->frch_root;
+ #ifdef BFD_ASSEMBLER
    fix = seg_info (now_seg)->frchainP->fix_root;
+ #else
+ #ifdef MANY_SEGMENTS
+   fix = segment_info[now_seg].fix_root;
+ #else
+   if (now_seg == SEG_DATA)
+     {
+       fix = data_fix_root;
+     }
+   else if (now_seg == SEG_TEXT)
+     {
+       fix = text_fix_root;
+     }
+   else
+     {
+       know (now_seg == SEG_BSS);
+       fix = bss_fix_root;
+     }
+ #endif
+ #endif
    subseg_set (current_seg, current_subseg);
  
    /* Look through the frags of the section to find the code alignment.  */