[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/23161] __bss_start, _end and _edata aren't marked as hidden

From: amodra at gmail dot com
Subject: [Bug ld/23161] __bss_start, _end and _edata aren't marked as hidden
Date: Thu, 10 May 2018 23:01:17 +0000


Alan Modra <amodra at gmail dot com> changed:

           What    |Removed                     |Added
                 CC|                            |amodra at gmail dot com

--- Comment #1 from Alan Modra <amodra at gmail dot com> ---
I agree that exporting these symbols doesn't seem to be useful.  I can't see a
good reason why anyone would want access to their values in shared libraries
external to the given shared library (and to choose a particular _edata say,
from among many possible shared libraries requires dlopen and dlsym).

Also, given that the standard scripts define these symbols for shared
libraries, it isn't simple for a shared library to access their values in the
executable.  Again, you'd need to use dlopen and dlsym.  So it probably isn't
that useful to export these symbols from an executable, but I'm less sure about
executables than I am about shared libraries.

You are receiving this mail because:
You are on the CC list for the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]