[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/18174] New: Improve documentation on Forced Output Section Align
From: |
sven.koehler at gmail dot com |
Subject: |
[Bug ld/18174] New: Improve documentation on Forced Output Section Alignment |
Date: |
Sat, 28 Mar 2015 13:47:22 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=18174
Bug ID: 18174
Summary: Improve documentation on Forced Output Section
Alignment
Product: binutils
Version: 2.25
Status: NEW
Severity: enhancement
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: sven.koehler at gmail dot com
I'm referring to
https://sourceware.org/binutils/docs-2.25/ld/Forced-Output-Alignment.html
The documentation given there is insufficient. An Output Section has two
addresses, the LMA and the VMA. It should be made clear ALIGN(x) effects the
VMA, and the VMA only. I believe, this might have been different in earlier
versions of binutils, where the LMA was also affected. If so, that should be
documented as well. The effect of ALIGN(x) on VMA and LMA can currently only be
understood by intense testing.
Also, ALIGN_WITH_INPUT keeps the difference between LMA and VMA intact, as the
documentation states. But again without a lot of testing, it's not clear what's
going on. It would be better to describe ALIGN_WITH_INPUT in a way that makes
clear what the effect on VMA and LMA is:
1) the VMA is aligned in the usual way (to the strictest alignment of the input
sections)
2) the LMA is not aligned, but instead padded (!) with the same amount that
added to the VMA to achieve the section's VMA alignment.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug ld/18174] New: Improve documentation on Forced Output Section Alignment,
sven.koehler at gmail dot com <=