search for: frecord

Hi llvm-dev, I have an implementation of -frecord-gcc-switches ready for Clang, and a named metadata node seemed like the correct way to approach this on the LLVM side. I have a review at https://reviews.llvm.org/D54487 which discusses some of the differences in implementation vs. GCC. A change to the set of "special" named metadata...

...command lines. What should the semantics be? During regular object linking, I assume the command lines are discarded. Maybe just code that up? > > On Tue, Nov 13, 2018 at 12:27 PM via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hi llvm-dev, > > I have an implementation of -frecord-gcc-switches ready for Clang, and a > named metadata node seemed like the correct way to approach this on the > LLVM side. I have a review at https://reviews.llvm.org/D54487 which > discusses some of the differences in implementation vs. GCC. A change to > the set of "special&q...

You should probably pull in some folks who implemented/maintain the feature for Darwin. I guess they aren't linking this info, but only communicating in the object file between tools - maybe they flag these sections (either in the object, or by the linker) as ignored/dropped during linking. That semantic could be implemented in ELF too by marking the sections SHF_IGNORED or something

...| 2 +- fs/nilfs2/namei.c | 8 +-- fs/nsfs.c | 2 +- fs/ntfs/inode.c | 15 +++--- fs/ntfs/mft.c | 3 +- fs/ntfs3/file.c | 6 +-- fs/ntfs3/frecord.c | 4 +- fs/ntfs3/inode.c | 14 ++--- fs/ntfs3/namei.c | 10 ++-- fs/ntfs3/xattr.c | 4 +- fs/ocfs2/acl.c | 6 +-- fs/ocfs2/alloc.c | 6 +-- fs/...