search for: writeto

...e) The frontend work seems to be largely dominated by ObjectFile::parse (as you would expect), though there is about 10% of total runtime slipping through the cracks here in various other "frontend" tasks. The backend work is split about evenly between scanRelocations and OutputSection::writeTo. InputSectionBase::relocate is only about 10% of the total runtime (part of OutputSection::writeTo). Some slightly cleaned up `perf report` output with some more details: https://reviews.llvm.org/P7972 So it seems like overall, the profile is basically split 3 ways (about 30% each): - frontend (r...

...o a function at .text segment (in this case frame_dummy). I am trying to made this on lld, but current step sequence is: - Write::run \_ Write::createSections \_ Write::scanRelocs \_ Write::addReloc // Dynamic Relocation creation \_ Write::writeSections \_ OutputSectionBase::writeTo \_ InputSection::writeTo \_ InputSection::relocate \_ TargetInfo::relocateOne The problem is only at TargetInfo::relocate the target (aarch64) will see that the relocation is a R_AARCH64_ABS64 one and thus will need to create a dynamic R_AARCH64_RELATIVE relocatio...

...minated by ObjectFile::parse (as >> you would expect), though there is about 10% of total runtime slipping >> through the cracks here in various other "frontend" tasks. >> >> The backend work is split about evenly between scanRelocations and >> OutputSection::writeTo. InputSectionBase::relocate is only about 10% of the >> total runtime (part of OutputSection::writeTo). >> >> Some slightly cleaned up `perf report` output with some more details: >> https://reviews.llvm.org/P7972 >> >> So it seems like overall, the profile is ba...

...ssert(false);` on line 386 below in ICF.cpp and all our tests pass. (https://github.com/llvm-mirror/lld/blob/master/ELF/ICF.cpp#L386) 2) In Relocations.cpp, all code inside `if`: https://github.com/llvm-mirror/lld/blob/master/ELF/Relocations.cpp#L1177 Is not covered by tests. 3) MicroMipsR6Thunk::writeTo(), MicroMipsR6Thunk::addSymbols(), MicroMipsR6Thunk::getTargetInputSection() are not covered. That seems to be all major places I saw in report. Now we probably can think about what we can do with that? * Ideal scenario I can imagine is that we could fix all the places and, for example, setup the...

tl;dr: it looks like we call SymbolBody::getVA about 5x more times than we need to Should we cache it or something? (careful with threads). Here is a link to a PDF of my Mathematica notebook which has all the details of my investigation: https://drive.google.com/open?id=0B8v10qJ6EXRxVDQ3YnZtUlFtZ1k There seem to be two main regimes that we redundantly call SymbolBody::getVA: 1. most

...in ICF.cpp and all our tests pass. > (https://github.com/llvm-mirror/lld/blob/master/ELF/ICF.cpp#L386) > > 2) In Relocations.cpp, all code inside `if`: > https://github.com/llvm-mirror/lld/blob/master/ELF/Relocations.cpp#L1177 > Is not covered by tests. > > 3) MicroMipsR6Thunk::writeTo(), MicroMipsR6Thunk::addSymbols(), > MicroMipsR6Thunk::getTargetInputSection() are not covered. > > That seems to be all major places I saw in report. > > Now we probably can think about what we can do with that? > * Ideal scenario I can imagine is that we could fix all the places...

...nfig.parseFrom(nut::NutFile( "/usr/local/ups/etc/ups.conf", nut::NutFile::READ_ONLY)); std::cout << "my-ups description: " << config.getDescription("my-ups") << std::endl; // ... config.setDriver("my-ups", "snmp-ups"); config.writeTo(nut::NutFile( "/usr/local/ups/etc/ups.conf", nut::NutFile::WRITE_ONLY)); Regards, vasek -- V?clav Krpec Network UPS Tools project Eaton Opensource Team ----------------------------- Eaton Elektrotechnika s.r.o. ~ S?dlo spolecnosti, jak je zaps?no v rejstr?ku: Kom?rovsk? 2406, Pra...

...at org.apache.tika.server.resource.TikaResource.parse(TikaResource.java:409) Nov 15 15:59:41 test.loc tika[35696]: at org.apache.tika.server.resource.TikaResource$4.write(TikaResource.java:521) Nov 15 15:59:41 test.loc tika[35696]: at org.apache.cxf.jaxrs.provider.BinaryDataProvider.writeTo(BinaryDataProvider.java:177) Nov 15 15:59:41 test.loc tika[35696]: at org.apache.cxf.jaxrs.utils.JAXRSUtils.writeMessageBody(JAXRSUtils.java:1472) Nov 15 15:59:41 test.loc tika[35696]: at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.serializeMessage(JAXRSOutInterceptor.java:...

On 11/15/20 12:21 PM, John Fawcett wrote: > I'm using tika-server.jar installed as a service yup. same here. atm, listening on localhost, with Dovecot -> Tika direct, no proxy. similarly fragile under load. throwing ~10 messages with .5-5MB attachments at it at once causes all sorts of complaints. one at a time seems OK ... > Dovecot currently implements separate integrations,

On Tue, Feb 21, 2017 at 2:05 PM, Rafael Avila de Espindola via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Carlo Kok <ck at remobjects.com> writes: > > > On 2017-02-21 20:33, Rafael Avila de Espindola wrote: > >>> Input files: > >>> https://www.dropbox.com/s/8yn3dggx05atn47/binLinux.zip?dl=0 > >> > >> If you pass --reproduce

...ent.html> -------------- next part -------------- diff --git a/ELF/SyntheticSections.cpp b/ELF/SyntheticSections.cpp index 19326bc..05fb9e3 100644 --- a/ELF/SyntheticSections.cpp +++ b/ELF/SyntheticSections.cpp @@ -1031,6 +1031,7 @@ template <class ELFT> void RelocationSection<ELFT>::writeTo(uint8_t *Buf) { // in account 'local' and 'global' GOT entries. P->r_offset += In<ELFT>::MipsGot->getTlsOffset(); P->setSymbolAndType(Rel.getSymIndex(), Rel.Type, Config->Mips64EL); + errs() << "NAME: " << Rel.Sym->get...

By the way, since this is an optional code relaxation, we can think about it later. The first thing I would do is to add RISC-V support to lld without code shrinking relaxations, which I believe is doable by at most a few hundreds lines of code. On Wed, Jul 12, 2017 at 3:21 AM, Rui Ueyama <ruiu at google.com> wrote: > On Tue, Jul 11, 2017 at 9:14 PM, Bruce Hoult via llvm-dev < >

Are you suggesting other linker jobs such as creating _end symbols to the linker script? The linker script support was implemented after we wrote the current Writer class, so it is somewhat "plugged in" to the Writer. It might not be the best design, and not many other options have been explored. So there might be room to improve code by moving work loads from the Writer to the