similar to: Linking the FreeBSD base system with lld

On 26 July 2018 at 15:52, Ed Maste <emaste at freebsd.org> wrote: > On 27 February 2018 at 09:06, Ed Maste <emaste at freebsd.org> wrote: >> >> A number of companies are shipping products based on FreeBSD/arm, on >> v5 and up. As far as I know those using older processors are also >> using older versions of FreeBSD (with a toolchain based on GCC and >>

Checking up on this change: On Wed, 29 Mar 2023 at 19:38, Ed Maste <emaste at freefall.freebsd.org> wrote: > > From: Ed Maste <emaste at FreeBSD.org> > > By convention settings in ssh_config are shown with a commented out > default. > > Fixes: 6cb52d5bf771 ("upstream: make CheckHostIP default to 'no'...") > --- > ssh_config | 2 +- > 1

On 26 July 2018 at 18:05, Ed Maste <emaste at freebsd.org> wrote: > On 26 July 2018 at 11:08, Peter Smith <peter.smith at linaro.org> wrote: >> On 26 July 2018 at 15:52, Ed Maste <emaste at freebsd.org> wrote: >>> On 27 February 2018 at 09:06, Ed Maste <emaste at freebsd.org> wrote: >>>> >>>> A number of companies are shipping

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

On 27 February 2018 at 05:29, Peter Smith via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I've got some downstream patches > for v5 and v6 support (limit branch range, and use different > instructions in stubs), however I don't think anyone has actually > needed support yet. For FreeBSD we're on a path to having Clang + lld as our toolchain for all Tier-1

On 13 March 2018 at 16:51, Ed Maste <emaste at freebsd.org> wrote: > On 7 February 2018 at 01:20, Chandler Carruth via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> I've landed the patch in r324449. > > To confirm, this change *did not* make it into 6.0.0, correct? I'm > looking at adding the external thunk for FreeBSD now, and we have > 6.0.0 in

On Sat, 5 Nov 2022 at 14:49, Ed Maste <emaste at freebsd.org> wrote: > > From: Yuichiro Naito <naito.yuichiro at gmail.com> > > If the following functions are available, > add an additional check if users are allowed to login imposed by login class. > > * auth_hostok(3) > * auth_timeok(3) > > These functions are implemented on FreeBSD. > > --- >

On 27 February 2014 00:05, Simon Atanasyan <simon at atanasyan.com> wrote: > > Install tool invokes strip. GNU install allows to configure which > strip to use (--strip-program). In general (for example on FreeBSD) it > is not possible and install always runs just 'strip'. In case of > cross-compilation that leads to the error. Actually it is possible on FreeBSD --

I've started the process of bringing LLVM's libunwind into the FreeBSD base system[1]. As part of that process we've tested building the approximately 25,000 third party software packages in the FreeBSD ports collection against a modified FreeBSD with libunwind included[2]. Of course, I wouldn't expect much in the way of build failures -- I'd expect any issues to be largely

One remaining blocking issue for linking FreeBSD with lld is the inability to build the bootloader components. We have a patch[1] in review to address one of the problems by switching to using a linker script instead of GNU ld's -N option. Another issue is that some bootloader components are created by the linker directly as binary objects, using --oformat binary. (Other bootloader components

A change between r231216 and r231221 causes an assertion failure on the LLDB FreeBSD bot. The compiler is FreeBSD's in-tree one: FreeBSD clang version 3.5.1 (tags/RELEASE_351/final 225668) 20150115 First failing build: http://lab.llvm.org:8011/builders/lldb-x86_64-freebsd/builds/4668/steps/compile/logs/stdio Assertion: Assertion failed: ((!DD->isTrivial() ||

On 24 April 2015 at 16:32, Saleem Abdulrasool <compnerd at compnerd.org> wrote: > > Until a git mirror is setup, we will need to use subversion ... What needs to happen in order to get the libunwind git mirror set up?

All the tools in ./BuildTools/Release+Asserts/bin/ Are host tools. Since I'm not doing the make install on the target, then strip does not know about these. It knows enough to install these as xxx-host but not enough to not call strip. On 02/27/2014 06:19 AM, Joerg Sonnenberger wrote: > On Thu, Feb 27, 2014 at 08:53:20AM -0500, Ed Maste wrote: >> On 27 February 2014 00:05,

Dear everyone, It's not quite time to start the 3.8 release process, but it's time to start planning. Please let me know if you want to help with testing and building release binaries for your favourite platform. (If you were a tester on the previous release, you're cc'd on this email.) I propose the following schedule for the 3.8 release: - 13 January: Create 3.8 branch.

On 13 August 2016 at 11:16, Davide Italiano via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > There's enough AArch64 to allow lld to self-host and to finish a build > of the base system on FreeBSD. Last we (I and Rafael) checked, it was > mid-june timeframe, but nothing changed since then. FYI when trying to link the FreeBSD/arm64 kernel now I receive tens of thousands of

On Jan 19, 2017 2:48 AM, "Ed Maste" <emaste at freebsd.org> wrote: On 4 January 2017 at 13:34, Peter Smith via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I'm about to start working on range extension thunks in lld. This is > an attempt to summarize the approach I'd like to take and what the > impact will be on lld outside of thunks. Now that LLD works

On 30 April 2015 at 10:06, Hal Finkel <hfinkel at anl.gov> wrote: >> >> I'd like to resurrect the discussion on replacing libgomp with >> libiomp as the default OpenMP runtime library linked with -fopenmp. >> >> >> For reference, the previous discussion is accessible there: >>

One of the issues I reported in using lld as the FreeBSD base system linker is that the base system currently uses ld -r to convert a binary file (device firmware image) into an ELF object: > A tool for loading firmware into a wireless USB device includes a > built-in copy of the firmware image, and the image is converted to an > ELF file using ld -r. The invocation is: ld -b binary -d

On 27 May 2015 at 12:29, Justin Bogner <mail at justinbogner.com> wrote: > Mehdi Amini <mehdi.amini at apple.com> writes: >> Hi Manuel, >> >> I like Phabricator for code review much much more than emails. Let me know how >> I can help (I’m not afraid of PHP). > > Chandler updated the llvm phabricator doc to point at what we're deploying: > >

On Mon, 1 Apr 2019 at 16:16, JF Bastien via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I haven’t documented FreeBSD / NetBSD / Fedora / MacOS / MSVC, and nobody complained at the BoF. I’d like to understand if we should care about documenting these: ideally the toolchain update policy would list which platforms need to be considered and how far back in time is relevant. FreeBSD