| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good. Remember to use proper labeling for the release notes and documentation purposes.
Sorry, something went wrong.
This commit adds real support for GNU version-script node dependencies
instead of warning and discarding them. A dependent node such as
V1 { ... };
V2 { ... } V1;
previously triggered `Dependent nodes are not supported` and the
dependency was silently dropped. Now, a dependency is validated against
already-registered named version nodes when symbol versioning is
enabled, rejecting unknown, forward, and self references the same way
GNU ld does. Symbol scope, version ID assignment, and `.gnu.version`
continue to be driven purely by node order and symbol rules, so this is
metadata-only.
The `.gnu.version_d` writer now emits a dependency as an additional
`Verdaux` entry on the dependent version definition.
Resolves qualcomm#1581
Signed-off-by: Parth Arora <partaror@qti.qualcomm.com>
| Back | FazBrowse Home | New Git URL |
This commit adds real support for GNU version-script node dependencies instead of warning and discarding them. A dependent node such as
V1 { ... }; V2 { ... } V1;previously triggered Dependent nodes are not supported and the dependency was silently dropped. Now, a dependency is validated against already-registered named version nodes when symbol versioning is enabled, rejecting unknown, forward, and self references the same way GNU ld does. Symbol scope, version ID assignment, and .gnu.version continue to be driven purely by node order and symbol rules, so this is metadata-only.
The .gnu.version_d writer now emits a dependency as an additional Verdaux entry on the dependent version definition.
Resolves #1581