similar to: LLVM 8 + Mavericks?

W dniu 2019-04-04 o 09:18, Tim Northover pisze: > On Wed, 3 Apr 2019 at 19:05, Audiovisart via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Does LLVM 8 work in macOS 10.9.5? > It should do. The released binaries appear to have been compiled so > they can run on that version, and Apple Clang 6.0 (from the newest > Xcode that runs on 10.9) meets the build

Is the new EH scheme completely compatible with the existing linker in Xcode 4.1? I am finding that today's changes break the ability to link xplor-nih with dragonegg under FSF gcc 4.6.2... de-g++46 -c thread.cc -O3 -ffast-math -funroll-loops -g -DX_MMAP_FLAGS=0 -DFORTRAN_INIT -fno-common -DDARWIN -D_REENTRANT -DNDEBUG -I/Users/howarth/xplor-nih-2.27/vmd/

On 04/03/2020 21:45, Jim Ingham via llvm-dev wrote: > As you have seen, different machine architectures do different things after hitting a trap. On x86_64, the trap instruction is executed, and then you stop, so the PC is left after the stop. On arm64, when execution halts the pc is still pointing at the trap instruction. > > I don't think lldb should be in the business of telling

On 12 September 2016 at 16:23, Rui Ueyama <ruiu at google.com> wrote: > What's the motivation to not build COFF and Mach-O parts? If you don't need > it, you could just leave it. Are you trying to reduce the executable size? It was just easier to remove coff::link() and mach_o::link() from lld.cpp than to add them to our own build infrastructure

Hi, I'm noticing an unexpected difference between targets when I hit a dbgtrap in the debugger. Consider this simple llvm function: define void @do_break() { entry: call void @llvm.debugtrap() ret void } If I compile that with llc and use lldb to launch a program that calls it, on x86_64 linux (Ubuntu 18.04), here's what I see at the stop: Process 130404 stopped * thread #1,

LLDB currently uses a client-server architecture.  That appears fine, but runs into an annoying security problem: other users on the same machine can connect to the TCP socket and take over LLDB and thus the user’s system.  This means that LLDB is useless in multiuser enviromnents on Linux, such as academic computer labs. The immediate problem can be solved by using either HMAC authentication of

Hi Tim. Thank you for taking to time to comment on the background! I will definitely study lldb and remote JIT for ideas.  I worry that I will not be able to pre-link on the host side because the host cannot(?) know the final memory layout of code on the client side, especially when there are multiple plugins being loaded in different combinations on the host and client.  Is that an

We're in the process of importing lld into FreeBSD (along with our Clang 3.9 update project). For now I've removed all but the ELF linker[1]. We have no need for COFF and Mach-O, and we have a bespoke build system for all of our contrib code. I didn't bother adding build support for the source files for non-ELF linkers. Is this something that'd be reasonable / desirable to have

On Tue, Dec 13, 2016 at 8:10 PM, Andrew Kelley <superjoe30 at gmail.com> wrote: > > On Tue, Dec 13, 2016 at 10:59 PM, Sean Silva via llvm-dev < > llvm-dev at lists.llvm.org> wrote: >> >> Yes. Rui has bent over backwards every time a real user has come to us >> and said "we need X". The historical precedent here is that LLD is open to >> many

Would you say that embedding the LLVM linker is a practical way to get the required dynamic linking capabilities on the bare-metal side? Orthogonal Devices Tokyo, Japan www.orthogonaldevices.com On 27/06/2019 19:06, Peter Smith wrote: > On Thu, 27 Jun 2019 at 10:36, Brian Clarkson via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hi Tim. >> >> Thank you for

On Tue, Dec 13, 2016 at 10:59 PM, Sean Silva via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > Yes. Rui has bent over backwards every time a real user has come to us and > said "we need X". The historical precedent here is that LLD is open to many > kinds of changes, but not on theoretical grounds. > > Admittedly this leads to a somewhat conservative design

Hello! Q1 Are there any resources or examples on embedding LLVM into an ARM-based bare-metal application?  Searching in this area only turns up information on how to use LLVM to target bare-metal when I want to compile LLVM for linking against a bare-metal application. Q2 Are there any memory usage benchmarks for LLVM across the common tasks (especially loading bytecode, doing the

On Tue, Jun 26, 2018 at 1:28 PM Adrian Prantl <aprantl at apple.com> wrote: > > > > On Jun 26, 2018, at 11:58 AM, Zachary Turner via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > Hi all, > > > > We have been thinking internally about a lightweight llvm-based > ptracer. To address one question up front: the primary way in which this

Hey, I''m designing an app which displays the events near a user in RoR. I''m using the beat forum to facilitate user management/sessions/etc. I''ve edited the sessions table in the Beast database to contain a "session_location" value and what I''d like to do is to set this to the users location when they log in. This would allow them to change their

https://bugzilla.mindrot.org/show_bug.cgi?id=1466 Summary: Document that scp follows symbolic links Classification: Unclassified Product: Portable OpenSSH Version: 5.0p1 Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P2 Component: scp AssignedTo: bitbucket at

Hey guys, so I think I''ve done my installation of the beast forum correctly. Its done the database migration and all the tables look fine. Now, when I run ruby script/server and point my browser at http://localhost:3000/ I get a "500 Internal Server Error" error. Anybody know whats causing this? I''ve been trying to work it out for ages now and its wrecking my head

LLVM Weekly - #219, Mar 12th 2018 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/219>. Welcome to the two hundred and nineteenth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by [Alex

[redirecting to nut-upsuser since we hardly use the packaging list anymore] On May 15, 2014, at 9:20 AM, Jose Vigil wrote: > Hi friends, > > I?m looking for an already compiled .pkg NUT Client to be installed in a Mavericks iMac. Can someone, please point me to place where I can find it? We don't have any official ones. If anyone else has compiled one, please feel free to share

We run a dovecot mailserver. One of the clients I use is a Mac Laptop. Recently I upgraded from Mountain Lion (10.8) to Mavericks (10.9). Under 10.8 it worked fine. On 10.9 it syncs up when I invoke the client, but after a while stops getting updates. Most of my mail clients are on Linux (thunderbird) or Android (K9) and I admit that several run against my very large INBOX simultaneously. The

On Sat, Nov 22, 2014 at 07:05:11PM +0300, Vladimir "Equidamoid" Shapranov wrote: > I've got the following error when tried to compile tinc-1.0.24: [...] > Undefined symbols for architecture x86_64: > "_res_9_init", referenced from: > _main_loop in net.o > ld: symbol(s) not found for architecture x86_64 > > The symbol is exported in