- User Since
- Sep 24 2015, 8:50 PM (204 w, 6 h)
Aug 21 2018
May 10 2018
Apr 10 2017
Mar 31 2017
Updated patch with reverting the previous change.
Can you please merge the change ?
Mar 30 2017
Mar 29 2017
Thanks Peter, I will revise the lld test and recommit the change.
Mar 28 2017
Check for section permissions to account for test cases that rely on the behavior.
The changes are causing a problem as tests in lld have been written with the assumption that objdump will be able to dump data inside of a text section. I am hence uploading a new patch that checks for section permissions as well. Please let me know how you want to go about it ?
Mar 27 2017
Thanks Tim for the detailed review.
Mar 22 2017
Address comments from Tim. I will make the AArch64 changes as a separate commit.
Mar 21 2017
Mar 14 2017
Does AARCH64 use Mapping symbols anytime ? I havent seen GCC doing that.
Mar 13 2017
Mar 8 2017
Update with comments from Tim and address the issue that he mentioned.
I was discussing with Colin L and found a way to handle your case. Will post a patch soon.
Though, The testcase that you have mentioned is a genuine test and GCC supports it!.
I see what you are saying.
Updated with review comments from Tim.
It looks like gcc doesnot purely go by whether section has data or not. It also checks for section permissions.
Mar 7 2017
I totally forgot about your comment, I will respond to you with a testcase shortly.
Ah ok. Thanks for the info. If the input is 'C', the extent to which a non allocatable section that can contain data and code mixed is really a corner case, unless the author does inline assembly ?
When I checked with GCC (Using tests) the behavior seems to be non allocatable sections do not have mapping symbols.
May 9 2016
I was trying to debug a problem with the usage of FileOutputBuffer where the memory contents are not being synced to disk. I traced every call in FileOutputBuffer and none of the calls return an error, but the file is not synced. This happens on windows systems with FAST IO enabled. Resizing the underlying file makes the problem disappear.
May 5 2016
Mar 24 2016
r_offset This member gives the location at which to apply the relocation action. For a relocatable file, the value is the byte offset from the beginning of the section to the storage unit affected by the relocation. For an executable file or a shared object, the value is the virtual address of the storage unit affected by the relocation.
Mar 17 2016
r_offset is being modeled as per the ELF spec IMO and looks correct. GNU objdump does show relocations when there are relocation sections, that point to the section that needs relocation.
Oct 26 2015
How are symbols resolved when there are multiple --start-group and --end-group options currently ? Which symbol is picked when there is a unresolved symbol from the second group ?
Oct 23 2015
I am trying to say without --start-group and --end-group, the linker would have produced an unresolved symbol.
Thanks Ruiu, Bigcheese. It would become confusing for the user when migrating from the GNU linker.
Oct 16 2015
Sep 28 2015
Any other comments ?, If not I will go ahead and commit this change and continue getting the Atom model for ELF
Sep 26 2015
Sep 24 2015
Thanks for the info, LGTM.