search for: emaste

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...

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_...

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: >>>> &g...

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 externa...

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 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...

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?

Does FreeBSD have fallocate(2) or equivalent? On Mon, Oct 30, 2017 at 4:32 PM, Ed Maste <emaste at freebsd.org> wrote: > On 23 October 2017 at 18:49, Rui Ueyama via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > >> > >> BTW, posix_fallocate() might provide better portability and decrease the > >> likelihood of falling back on ftruncate(). > >...

On Fri, 11 Nov 2022 at 11:05, Ed Maste <emaste at freebsd.org> wrote: > > We had one more report from Coverity Scan after we brought 9.1p1 into > the FreeBSD base system. It complains that calls like "path1 = > make_absolute_pwd_glob(path1, *pwd);" in sftp.c leak the allocation. I see this same issue has since been rep...

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 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

On 16 January 2017 at 15:31, Sean Silva <chisophugis at gmail.com> wrote: > Do we have any open projects on LLD? > > I know we usually try to avoid any big "projects" and mainly add/fix things > in response to user needs, but just wondering if somebody has any ideas. > > Some really generic/simple stuff I can think of: > 1. trying out LLD on a large program

On Wed, Mar 15, 2017 at 6:02 PM, Ed Maste <emaste at freebsd.org> wrote: > Note that even if/when we get changes incorporated into libtool it > will still take a long time for the change to appear in new releases > of software packages using libtool. A downstream patch to the libtool > package in various operating systems or distri...

On 28 October 2016 at 18:12, Ed Maste <emaste at freebsd.org> wrote: > It should be possible to search the path for ld.lld first, then ld, > but to me it seems like it will just be more confusing. Hum, for me it would be less confusing. :) GCC uses bfd by default, LLVM uses LLD. If you want to change, use -fuse-ld. What would be co...

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: >>

On 19 April 2016 at 06:59, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi Dima, > > Adhemerval is working on AArch64 support, and it should be mostly > there, though some missing TLS support. He should know more. Here's some info on TLS. Review D18960 has the initial implementation for TLSDESC support: http://reviews.llvm.org/D18960 I've been

Hi, I tried to use linker script with lld (this script works just file with GNU ld). I got a problem with defining new symbols and assign values (addresses) to them. For instance I got the following code in the linker script: SECTIONS { _exec_sym = 0; ... After using lld command with the --script option I got the following error: line 3: : expected, but got = _exec_sym = 0; ^ As

We had one more report from Coverity Scan after we brought 9.1p1 into the FreeBSD base system. It complains that calls like "path1 = make_absolute_pwd_glob(path1, *pwd);" in sftp.c leak the allocation. All make_absolute_pwd_glob() calls but one are of that form, so perhaps have it consume and free the first arg, as below (and https://reviews.freebsd.org/D37253)? diff --git