Blame binutils-rh1247126.patch

dffe617
diff -Nrup a/bfd/elf.c b/bfd/elf.c
dffe617
--- a/bfd/elf.c	2015-07-28 10:52:10.941754850 -0600
dffe617
+++ b/bfd/elf.c	2015-07-28 10:53:34.725982912 -0600
dffe617
@@ -4081,11 +4081,18 @@ _bfd_elf_map_sections_to_segments (bfd *
dffe617
 	      new_segment = TRUE;
dffe617
 	    }
dffe617
 	  else if ((last_hdr->flags & (SEC_LOAD | SEC_THREAD_LOCAL)) == 0
dffe617
-		   && (hdr->flags & (SEC_LOAD | SEC_THREAD_LOCAL)) != 0)
dffe617
+		   && (hdr->flags & (SEC_LOAD | SEC_THREAD_LOCAL)) != 0
dffe617
+		   && ((abfd->flags & D_PAGED) == 0
dffe617
+		       || (((last_hdr->lma + last_size - 1) & -maxpagesize)
dffe617
+			   != (hdr->lma & -maxpagesize))))
dffe617
 	    {
dffe617
-	      /* We don't want to put a loadable section after a
dffe617
-		 nonloadable section in the same segment.
dffe617
-		 Consider .tbss sections as loadable for this purpose.  */
dffe617
+	      /* We don't want to put a loaded section after a
dffe617
+		 nonloaded (ie. bss style) section in the same segment
dffe617
+		 as that will force the non-loaded section to be loaded.
dffe617
+		 Consider .tbss sections as loaded for this purpose.
dffe617
+		 However, like the writable/non-writable case below,
dffe617
+		 if they are on the same page then they must be put
dffe617
+		 in the same segment.  */
dffe617
 	      new_segment = TRUE;
dffe617
 	    }
dffe617
 	  else if ((abfd->flags & D_PAGED) == 0)