This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [gold commit] Place copy relocations in .dynbss when target is read-only
- From: Andreas Schwab <schwab at linux-m68k dot org>
- To: Cary Coutant <ccoutant at gmail dot com>
- Cc: Binutils <binutils at sourceware dot org>
- Date: Wed, 28 Dec 2016 18:35:30 +0100
- Subject: Re: [gold commit] Place copy relocations in .dynbss when target is read-only
- Authentication-results: sourceware.org; auth=none
- References: <CAJimCsGZEaBDEn19aAJVumw+sgg6caTaubOCWz+sa3ZhNdLhRQ@mail.gmail.com> <m2vau4v4of.fsf@linux-m68k.org> <CAJimCsEWCqWckS0+Gne5c4rcS2+=1Ocb9SyXpBww4h3UvY6_XQ@mail.gmail.com>
On Dez 28 2016, Cary Coutant <ccoutant@gmail.com> wrote:
>>> 2016-12-27 Cary Coutant <ccoutant@gmail.com>
>>>
>>> gold/
>>> PR ld/20995
>>> * copy-relocs.cc (Copy_relocs::make_copy_reloc): Use .dynbss for
>>
>> s/dynbss/dynrelro/
>
> Fixed, thanks!
There was a reference in a comment left.
Andreas.
diff --git a/gold/copy-relocs.h b/gold/copy-relocs.h
index 92b2ceb1e8..f5cd0a5529 100644
--- a/gold/copy-relocs.h
+++ b/gold/copy-relocs.h
@@ -155,8 +155,9 @@ class Copy_relocs
// The dynamic BSS data which goes into the .bss section. This is
// where writable variables which require COPY relocations are placed.
Output_data_space* dynbss_;
- // The dynamic read-only data, which goes into the .dynbss section. This
- // is where read-only variables which require COPY relocations are placed.
+ // The dynamic read-only data, which goes into the .data.rel.ro section.
+ // This is where read-only variables which require COPY relocations are
+ // placed.
Output_data_space* dynrelro_;
};
--
2.11.0
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."