similar to: [LLVMdev] Patch to determine whether an LLVM archive file really is such

Here is the bulk of the sanitizing. My residual doubts center around the question whether we still do/want to support (un)compressed *byte*code in 2.0/2.1. I need a definitive word on this to proceed. My understanding is that bytecode is already gone, but there are still some functions/enums that really deal with *byte*code (instead of *bit*code). I did not touch those areas, so the attached

Hi, I have started to work on support for Reading archive libraries in lld and thought of using the llvm/lib/ArchiveReader for this. The ArchiveReader doesnot fully support GNU archive libraries (thin archives), do you think we should continue using llvm/lib/ArchiveReader ? I was chatting with Michael and looks like there have been discussions and small sketches done on reading archive

On Oct 19, 2012, at 3:41 PM, Shankar Easwaran wrote: > Hi, > > I have started to work on support for Reading archive libraries in lld and thought of using the llvm/lib/ArchiveReader for this. > > The ArchiveReader doesnot fully support GNU archive libraries (thin archives), do you think we should continue using llvm/lib/ArchiveReader ? > > I was chatting with Michael and

Hi Nick, Here is my understanding, 1) lld-core creates a ReaderOptionsArchive class with the (Reader, CommandLine options flag) 2) lld-core creates an object of type ReaderArchive(ReaderOptions), that users would subclass (off ArchiveLibraryFile) a) GNUArchiveLibrary b) BSDArchiveLibrary b) MachOArchiveLibrary c) COFFArchiveLibrary 3) ReaderArchive has two functions

On Oct 23, 2012, at 1:01 PM, Shankar Easwaran wrote: > Hi Nick, > > Here is my understanding, > > 1) lld-core creates a ReaderOptionsArchive class with the (Reader, CommandLine options flag) > 2) lld-core creates an object of type ReaderArchive(ReaderOptions), that users would subclass (off ArchiveLibraryFile) > a) GNUArchiveLibrary > b) BSDArchiveLibrary >

Hi I have some odd problem with running dovecot. Program dies with message in maillog: Mar 31 21:04:02 test-box dovecot: Dovecot starting up Mar 31 21:04:04 test-box dovecot: execv(imap-login) failed: Resource temporarily unavailable Mar 31 21:04:04 test-box dovecot: execv(imap-login) failed: Resource temporarily unavailable Mar 31 21:04:04 test-box dovecot: Login process died too early -

Hi everyone, I am fairly new to LLVM, I'm working on a new backend. I am trying to add information to a specific instruction using the .symtab in the ELF format. I've been searching through the LLVM source code trying to find a way to do such a thing. Can anyone help me with some directions or point me to some documents in the matter. Thanks, Liad. -------------- next part --------------

Hey Paul, first of all thank you for taking the time to answer me, if I understand you correctly, I need to modify the instruction it self so one of it's operands is a symbol, and then at MC layer handle that symbol and add an entry to the symtab for that label? What kind of symbol should I use doing such thing? external symbol or MCSymbol? I was trying to find where in the code during the MC

Hi Liad, I'm not an expert in MC, but what you describe doesn't sound any different from how you would handle a branch instruction. Create an MCSymbol that represents the address of the target instruction; use that symbol as an operand in the referencing instruction; emit the symbol as a label just prior to emitting the target instruction. The second and third steps can occur in either

lld/test/ELF/invalid/symtab-sh-info.s (check-lld-elf) is recently flaky on Windows, e.g. https://reviews.llvm.org/harbormaster/unit/view/192869/ http://45.33.8.238/win/27684/step_10.txt It fails like every 3 or 4 builds. Could someone with a Windows machine check what is going on? Is that due to output non-determinism (just my guess) in yaml2obj.exe? -------------- next part -------------- An

Hi! If there is a string table for section headers, it also gets loaded. Therefore take it into account in size calculation for kernel symtab. Also there is no need to call elf_set_verbose() a second time after elf_init() (First call happens within elf_init()). Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> Keir: Can you also apply changeset 15672 and this patch to Xen

On Fri, May 15, 2015 at 5:11 AM, Dave Bozier <seifsta at gmail.com> wrote: > > Are you sure about the additional I/O? With native symtab, existing > tools just need to read those, while plugin based approach needs to read > bit code section to feedback symbols to the tool. > > The additional I/O will be quite big if you are going to emit the full > symbol table. Looking

According to https://reviews.llvm.org/D88348#2344466, that diff should fix the failure. From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Fāng-ruì Sòng via llvm-dev <llvm-dev at lists.llvm.org> Reply-To: Fāng-ruì Sòng <maskray at google.com> Date: Tuesday, November 10, 2020 at 10:13 PM To: LLVM Developers Mailing List <llvm-dev at lists.llvm.org> Cc: Nico

This adds [f]getc() and fgets() for parsing config files. Probably hard to avoid. Still trying to decide if I actually want to add system() or not. -hpa

Hello, I am receiving this error: assert(Slot != -1 && "Value in symtab but has no slot number!!"); While trying to generate a module at run time using LLVM classes. Specifically with an instance of StoreInst class. After I generate all the instructions, I try to save the Module to bytecode, but I receive that error in the method 'outputSymbolTable' Does anyone

Hi, I am trying to write a simple interpreter. I am trying to generate LLVM IR for assignment operation. The code for the generation part looks like this llvm::Value* codeGenSymTab(llvm::LLVMContext& context) { > printf("\n CodeGen SymTab \n"); > Value *num = ConstantInt::get(Type::getInt64Ty(context), aTable.value, > true); > Value *alloc = new

Great, thanks! Those results are about roughly what I was expecting. I assume "compilation time" is actually just the link time? I find it particularly interesting that the DWARFLinker rewriting solution produces the same size improvement in .debug_line as the fragmented DWARF approach. That suggests that in that case, fragmented DWARF output is probably about as optimal as it can get.

Hi Ricardo, Yes, its because you have an invalid module. You should run Module::verify before attempting to write the bytecode. This will pinpoint the problem for you. However, I think I know what's going on: you've left an object (a Value not a Type) in the symbol table that is not in the Module. Not quite sure how you do that, but I suppose its possible if you manipulated the symbol

When LLD builds a shared library for x86_64 it puts _GLOBAL_OFFSET_TABLE_ to the both .symtab and .dynsym and defines it as a GLOBAL symbol. If later this shared library participates in executable file linking and GNU BFD linked is used for that, this linker shows an error: /usr/bin/ld: a.out: hidden symbol `_GLOBAL_OFFSET_TABLE_' in /usr/lib/x86_64-linux-gnu/crt1.o is referenced by DSO Gold

When in a controller, how would I determine which environment I am currently running in? (Development,Test,Production) Thanks, Don Mc -- Posted via http://www.ruby-forum.com/.