similar to: [LLVMdev] New executable format

I'm trying to build LLVM on OPENBSD current with today's svn (feb 23), and it fails to build with the following errors: llvm[2]: Compiling ELFWriter.cpp for Release build In file included from ELFWriter.cpp:51: /root/llvm/include/llvm/Target/TargetLoweringObjectFile.h:345: error: virtual outside class declaration /root/llvm/include/llvm/Target/TargetLoweringObjectFile.h:345: error:

Hello all, I am a LLVM newer who want to add a new backend(EBC) into LLVM. After coping the related files from another target and modifying it, I meet a problem when I build the project. The error message is as follows: ================================================================ [ 94%] Built target llvm-dis Linking CXX executable ../../bin/llvm-mc Undefined symbols:

----- Original Message ----- > From: "Jack Andersen via llvm-dev" <llvm-dev at lists.llvm.org> > To: "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Wednesday, November 16, 2016 10:39:53 PM > Subject: Re: [llvm-dev] [MC] Target-Independent Small Data Section Handling > > Just pinging this patch for review, particularly from PPC > maintainers:

Just pinging this patch for review, particularly from PPC maintainers: https://reviews.llvm.org/D26344 It's now rebased for the latest master commits, `check-all` test results match those of the upstream base. There is also a clang driver patch, extending PPC target support for the `-G` flag: https://reviews.llvm.org/D26345 And lld patch implementing the _SDA_BASE_ symbols and includes an

I've prepared a preliminary patch with the intention of implementing PPC-EABI subtarget features for applications that run in a standalone embedded environment. https://reviews.llvm.org/D26344 The most significant difference compared with the SVR4 ABI is the use of SDA (small data area). This allows full-word constants and data to be grouped into small-data sections accessed using relocated

hi, I am trying to build the llvm trunk with make. I am trying a debug build and I am ending with the following build error. /home/rajika/projects/llvm/llvm/lib/Target/TargetLoweringObjectFile.cpp: In member function ‘virtual bool llvm::TargetLoweringObjectFileMachO::shouldEmitUsedDirectiveFor(const llvm::GlobalValue*, llvm::Mangler*) const’:

Hello all, I am a LLVM newer who want to add a new backend(EBC) into LLVM. After coping the related files from another target and modifying it, I meet a problem when I build the project. The error message is as follows: ================================================================ [ 94%] Built target llvm-dis Linking CXX executable ../../bin/llvm-mc Undefined symbols:

On 05/02/2012 01:00 PM, Dave Zarzycki wrote: > Shea, > > Feasible? Sure, anything is feasible. A good idea? Not really. The internal lld file format is an _intermediate_ data structure designed to make creating the final executable straightforward and fast. It isn't designed to be an executable format itself. In fact, the reason why linkers can often be slow is because the

Shea, Feasible? Sure, anything is feasible. A good idea? Not really. The internal lld file format is an _intermediate_ data structure designed to make creating the final executable straightforward and fast. It isn't designed to be an executable format itself. In fact, the reason why linkers can often be slow is because the intermediate and final object file formats are conflated. davez On

Default Fedora Core 5 "server profile" with SELinux disabled. Downloaded from: http://bits.xensource.com/oss-xen/release/3.0.4-1/kernel-3.0.4-fc5/RPMS/i386/ xen-3.0.4.1-1.i386.rpm kernel-xen-2.6.16.33-3.0.4.1.i386.rpm xen-devel-3.0.4.1-1.i386.rpm Installed the rpms and updated grub.conf, then reboot... grub reports: Error 13: Invalid or unsupported executable

Hey, I built a 2.6.18.8-xen kernel and created the initial ram disk by following the instructions in README file in Xen source package. Then I put a entry for new kernel in /boot/grub/menu.lst (I am using CentOS 5). Here is the menu.lst: ########################################## default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-8.el5) root

This is somewhat a summary/continuation of an R bug report: (https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=14645) Illumina's cluster definition files (*.egt) are one of the proprietary and undocumented file formats used by their GenomeStudio line of products for genomic studies. snpMatrix 1.17.0.7 onwards (http://sourceforge.net/projects/outmodedbonsai/files/snpMatrix%20next/)

On 5/2/12 10:29 AM, Shea Levy wrote: > Hello, > > Would it be feasible to use the internal lld file format as the native > executable format for an OS? Are there performance or space > considerations that would make this a poor choice? By lld, do you mean the LLVM IR bitcode format, or are you referring to something else? As far as using LLVM IR as a format for executables, there

Hello List, we have a running (test) AD samba4 system running successful for several month. We are now trying to add more DCs to the mix and have a proper backup/desaster recovery strategy. Basically I wan't to adapt the samba_backup script found in the sources to backup everything via git into our repository. I understand that the best solution would be to tar everything before commit. In

Hello, Would it be feasible to use the internal lld file format as the native executable format for an OS? Are there performance or space considerations that would make this a poor choice? Cheers, Shea Levy P.S. please CC me on replies, I'm not subscribed.

Hello Johannes, Am 18.12.2014 um 12:23 schrieb johannesa: > Basically I wan't to adapt the samba_backup script found in > the sources to backup everything via git into our repository. > I understand that the best solution would be to tar > everything before commit. You don't have to use tar. But you have to ensure, that you have a backup, that includes the extended ACLs and

Just to mention and because I'm in doubt: The samba_backup script contains tdbdump for private folder to create online dumps of all ldb. But the dumps are smaller than the original. Is that ok? I'm in doubt regarding integrity. Am 20. Dezember 2014 10:59:59 MEZ, schrieb Marc Muehlfeld <mmuehlfeld at samba.org>: >Hello Johannes, > >Am 18.12.2014 um 12:23 schrieb johannesa:

> I think that the improved behavior for consts should be acceptable in the large model. But that's just me. By default, all constants should be in a special read-only section, and this section may be far from the text section. I'm working with JIT model or with only one object file. The code model, when all constants are near, we can call "LargeJIT". (Is it sounds better

Hey! I have big problem with my centos 5.1. I have two hard discs 500gig and 40gig and those are in RAID0. I would like to remowe the small 40gig hd and put new 500gig hd and i don't wan't raid0 anymore. How can i copy data from 40gig hd to 500gig hd and switch 40gig hd to new 500gig hd? Another question: Can i just copy all my files to windows laptop and if i wan't

On Wed, May 5, 2010 at 11:15 AM, Chris Lattner <clattner at apple.com> wrote: > On May 4, 2010, at 11:03 AM, Nathan Jeffords wrote: > ... We basically want one MCStreamer callback to correspond to one > statement in the .s file. This makes it easier to handle from the compiler > standpoint, but is also very important for the llvm-mc assembly parser > itself. > > This