public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Bryan Ford <baford@snake.cs.utah.edu>
To: gas2@cygnus.com
Subject: Patch to binutils-2.6 for MS-DOS BFD backend
Date: Mon, 05 Feb 1996 14:00:00 -0000	[thread overview]
Message-ID: <199602052159.OAA27950@snake.cs.utah.edu> (raw)

Here's a very small patch to the i386-msdos target,
which fixes a bug in my code that only recently made itself known,
and cleans up a few other things a little...

Thanks!
				Bryan

diff -crN binutils-2.6/bfd/i386msdos.c binutils-2.6-moss/bfd/i386msdos.c
*** binutils-2.6/bfd/i386msdos.c	Mon Nov  6 03:07:21 1995
--- binutils-2.6-moss/bfd/i386msdos.c	Wed Dec 20 12:45:55 1995
***************
*** 28,52 ****
  #include "libaout.h"
  
  #if 0
- typedef struct msdos_data_struct
-   {
- #if 0
-     srec_data_list_type *head;
-     unsigned int type;
- 
-     int done_symbol_read;
-     int count;
-     asymbol *symbols;
-     char *strings;
-     int symbol_idx;
-     int string_size;
-     int string_idx;
- #endif
-   }
- tdata_type;
- #endif
- 
- #if 0
  struct exe_header
  {
  	unsigned short magic;
--- 28,33 ----
***************
*** 95,100 ****
--- 76,83 ----
    /* Find the total size of the program on disk and in memory.  */
    for (sec = abfd->sections; sec != (asection *) NULL; sec = sec->next)
      {
+       if (bfd_get_section_size_before_reloc (sec) == 0)
+         continue;
        if (bfd_get_section_flags (abfd, sec) & SEC_ALLOC)
          {
  	  bfd_vma sec_vma = bfd_get_section_vma (abfd, sec)
diff -crN binutils-2.6/ld/scripttempl/i386msdos.sc binutils-2.6-moss/ld/scripttempl/i386msdos.sc
*** binutils-2.6/ld/scripttempl/i386msdos.sc	Thu Jun 22 20:05:04 1995
--- binutils-2.6-moss/ld/scripttempl/i386msdos.sc	Sat Jan 27 22:35:00 1996
***************
*** 14,25 ****
      ${RELOCATING+etext = .;}
      ${RELOCATING+_etext = .;}
      ${RELOCATING+__etext = .;}
-     ${PAD_TEXT+${RELOCATING+. = ${DATA_ALIGNMENT};}}
    }
-   ${RELOCATING+. = ${DATA_ALIGNMENT};}
-   .rodata  ${RELOCATING-0} : { *(.rodata)  }
    .data :
    {
      *(.data)
      ${CONSTRUCTING+CONSTRUCTORS}
      ${RELOCATING+edata  =  .;}
--- 14,23 ----
      ${RELOCATING+etext = .;}
      ${RELOCATING+_etext = .;}
      ${RELOCATING+__etext = .;}
    }
    .data :
    {
+     *(.rodata)
      *(.data)
      ${CONSTRUCTING+CONSTRUCTORS}
      ${RELOCATING+edata  =  .;}


				Bryan
---
Bryan Ford	baford@cs.utah.edu	University of Utah, CSS
`finger baford@schirf.cs.utah.edu' for PGP key and other info.


                 reply	other threads:[~1996-02-05 14:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199602052159.OAA27950@snake.cs.utah.edu \
    --to=baford@snake.cs.utah.edu \
    --cc=gas2@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).