search for: tomhughes

...hanging the default. On Thu, Apr 5, 2018 at 2:50 PM Andrew Kelley via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Confirmed that -no-rosegment worked around the issue. > > However, a valgrind developer says that perhaps LLD is generating strange > object files: > > <tomhughes> I suspect that is some extra ro segment in addition to the > normal rodata > <tomhughes> so without it you have two > <tomhughes> but I know nothing about lld > <tomhughes> but without an executable to examine/test it's hard to be sure > <andrewrk> the...

Confirmed that -no-rosegment worked around the issue. However, a valgrind developer says that perhaps LLD is generating strange object files: <tomhughes> I suspect that is some extra ro segment in addition to the normal rodata <tomhughes> so without it you have two <tomhughes> but I know nothing about lld <tomhughes> but without an executable to examine/test it's hard to be sure <andrewrk> the not working elf file has...

...5, 2018 at 2:50 PM Andrew Kelley via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Confirmed that -no-rosegment worked around the issue. >> >> However, a valgrind developer says that perhaps LLD is generating strange >> object files: >> >> <tomhughes> I suspect that is some extra ro segment in addition to the >> normal rodata >> <tomhughes> so without it you have two >> <tomhughes> but I know nothing about lld >> <tomhughes> but without an executable to examine/test it's hard to be sure >>...

As a frontend, what are the downsides of enabling --no-rosegment by default? So far the pro list is: * valgrind debug info will work by default What's on the con list? On Thu, Apr 5, 2018 at 5:16 PM, Shoaib Meenai <smeenai at fb.com> wrote: > It's more of a valgrind issue than an LLD issue, but you can work around > it by linking with --no-rosegment > > > >