search for: asb

...and it's empty: moloch*CLI> sip show registry Host Username Refresh State moloch*CLI> If i try, from 203, calling 201 this is what happens: ===========================8<=================================== moloch*CLI> Sip read: INVITE sip:201@asb.unisi.it SIP/2.0 Via: SIP/2.0/UDP 192.167.125.9:5062;branch=z9hG4bK78ED0E83 CSeq: 7665 INVITE To: <sip:201@asb.unisi.it> Content-Type: application/sdp From: "203" <sip:203@asb.unisi.it>;tag=2B558754 Call-ID: 499575437@192.167.125.9 Subject: sip:203@asb.unisi.it Content-Length:...

...192.167.125.12 D 255.255.255.255 5060 OK (3 ms) moloch*CLI> as you can see, 201 and 203 are on-line but, if i call from 203 to 201, i immediately go to voicemail instead of doing call to 201. Here's the SIP call flow: moloch*CLI> Sip read: INVITE sip:201@asb.unisi.it SIP/2.0 Via: SIP/2.0/UDP 192.167.125.9:5062;branch=z9hG4bK64FE3538 CSeq: 1114 INVITE To: <sip:201@asb.unisi.it> Content-Type: application/sdp From: "203" <sip:203@asb.unisi.it>;tag=1CE28F8 Call-ID: 1646594512@192.167.125.9 Subject: sip:203@asb.unisi.it Content-Length:...

...XPERIMENTAL_TARGETS_TO_BUILD. not > LLVM_TARGETS_TO_BUILD. I thought people had agreed to change that in > this release? > > There are also at least a couple of fairly important patches that it > would be good to get back-ported into the release branch if possible > > r352171 | asb | 2019-01-24 21:11:34 -0800 (Thu, 24 Jan 2019) | 12 lines > [RISCV] Custom-legalise i32 SDIV/UDIV/UREM on RV64M > > r352169 | asb | 2019-01-24 21:04:00 -0800 (Thu, 24 Jan 2019) | 24 lines > [RISCV] Custom-legalise 32-bit variable shifts on RV64 > > > Others that would be good,...

As many of you know, I have a growing series of patches for a RISC-V backend under/awaiting review <https://reviews.llvm.org/differential/?authors=asb&order=updated>, <http://github.com/lowrisc/riscv-llvm>. I'll be posting a larger status update on that work either later today or tomorrow, this RFC focuses on an issue that came up during review which I think may benefit from wider input. David Chisnall suggested that the backend...

On 14 November 2017 at 16:03, Alex Bradbury <asb at lowrisc.org> wrote: > Dear list, > > At the RISC-V BoF at the LLVM Dev Meeting and the longer working > session the day after, those of us working on RISC-V with LLVM decided > it would be worthwhile to schedule regular sync-up calls in order to > better co-ordinate ongoing...

On 23 November 2017 at 09:38, Alex Bradbury <asb at lowrisc.org> wrote: > On 14 November 2017 at 16:03, Alex Bradbury <asb at lowrisc.org> wrote: >> Dear list, >> >> At the RISC-V BoF at the LLVM Dev Meeting and the longer working >> session the day after, those of us working on RISC-V with LLVM decided >&gt...

Dear list, At the RISC-V BoF at the LLVM Dev Meeting and the longer working session the day after, those of us working on RISC-V with LLVM decided it would be worthwhile to schedule regular sync-up calls in order to better co-ordinate ongoing work between different developers. This is primarily to sync-up, share blocking issues and so on. I understand something similar was done during the

On Wed, 22 Jan 2020 at 19:55, Chris Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Jan 21, 2020, at 5:00 AM, Alex Bradbury <asb at lowrisc.org> wrote: > >> This all makes sense to me. > > > > That's correct, thanks for the feedback. > > > > I do like the idea from James of having the compiler always spit out a > > note when enabling the experimental extension, warning of its &gt...

...rs to be easier to follow. IMHO, this would be easier for external users that desire to modify the backend for their own custom extensions/instructions. On Fri, Aug 18, 2017 at 5:05 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk > wrote: > On 18 Aug 2017, at 10:55, Alex Bradbury <asb at asbradbury.org> wrote: > > > > I've demonstrated both the "conventional" approach > > <https://gist.github.com/asb/0c61ebc131076c6186052c29968a49 > 1d#file-riscvinstrinfo_conventional-td> > > and the "separate patterns" approach > &g...

...ay October 17th), I'm organising a longer working session. This will be held at a Qualcomm location in San Jose, between approximately 10am-4pm. Anyone interested in contributing to RISC-V support in LLVM projects is incredibly welcome. Food and refreshments will be provided. Please email me at asb at lowrisc.org to confirm attendance. I appreciate that the scheduling may not work for those travelling to the Bay Area just for the Dev Meeting. I've assumed that Tue 17th is likely to be no more likely to be unworkable than the Fri the 20th, but do let me know if you think I'm wrong abou...

On Mon, Aug 28, 2017 at 8:04 AM, Alex Bradbury <asb at asbradbury.org> wrote: > On 27 August 2017 at 00:01, Alex Bradbury <asb at asbradbury.org> wrote: >> Hi all. I'm assuming most people reading this email are familiar with LLVM's >> code review process <http://llvm.org/docs/DeveloperPolicy.html#code-reviews>...

Dear testers, 8.0.0-rc1 was just tagged (from the branch at r351980). It took a little longer than planned, but it's looking good. Please run the test script, share your results, and upload binaries. I'll get the source tarballs and docs published as soon as possible, and binaries as they become available. Thanks, Hans

How do I add to a trellis plot the best fit line from a robust fit? I can use panel.lm to add a least squares fit, but there is no panel.rlm function. -- Alan S Barnett <asb at mail.nih.gov> NIMH/CBDB

On 21 March 2018 at 20:07, Alex Bradbury <asb at lowrisc.org> wrote: > On 23 November 2017 at 09:38, Alex Bradbury <asb at lowrisc.org> wrote: >> On 14 November 2017 at 16:03, Alex Bradbury <asb at lowrisc.org> wrote: >>> Dear list, >>> >>> At the RISC-V BoF at the LLVM Dev Meeting and the lon...

...ontributors' at the LLVM Cauldron back in September. I intended to write it up as an RFC, but have only just got round to doing so. I've tried to make this email self-contained, but you may still want to look at the slides or recording of the lightning talk. Slides: https://speakerdeck.com/asb/can-we-improve-the-experience-of-first-time-llvm-contributors Video: https://www.youtube.com/watch?v=32fmbEI9WrM # The problem As a first-time contributor, it's easy to be put off during the patch submission process. e.g. the patch may sit unreviewed for weeks. Typically people new to the proj...

...ions of libstdc++ and new versions of clang: polly-amd64-linux polly-arm-linux Once fixed the toolchain bump should stick. > On Jan 31, 2019, at 2:07 PM, JF Bastien via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > >> On Jan 31, 2019, at 2:03 PM, Alex Bradbury <asb at asbradbury.org <mailto:asb at asbradbury.org>> wrote: >> >> On Tue, 29 Jan 2019 at 21:05, JF Bastien via llvm-dev >> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >>> >>> The patch is about ready to land, which...

On 11 May 2014 13:25, Alex Bradbury <asb at asbradbury.org> wrote: > On 6 May 2014 09:42, Jay Foad <jay.foad at gmail.com> wrote: >> I followed a link from LLVM Weekly to http://reviews.llvm.org/rL207598 and got: >> >> " >> Still Importing... >> >> This commit is still importing. Ch...

...r, you can read a HTML version of this email at <http://llvmweekly.org/issue/52>. Welcome to the fifty-second 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 Bradbury](http://asbradbury.org). Subscribe to future issues at <http://llvmweekly.org> and pass it on to anyone else you think may be interested. Please send any tips or feedback to <asb at asbradbury.org>, or @llvmweekly or @asbradbury on Twitter. This issue marks the end of one full year of LLVM Weekly....

...changes the ABI to keep the pointer in a reserved register. >> >> -Eli >> >> From: Evandro Menezes <evandro.menezes at sifive.com> >> Sent: Friday, March 20, 2020 12:28 PM >> To: Eli Friedman <efriedma at quicinc.com> >> Cc: Alex Bradbury <asb at lowrisc.org>; llvm-dev <llvm-dev at lists.llvm.org> >> Subject: [EXT] Re: [llvm-dev] RISC-V LLVM sync-up call 19 Mar 2020 >> >> Hi, Eli. >> >> If I’m following correctly, there are two size-limited areas. One area, limited to 2GB, is the “text” area. Th...

..., you can read a HTML version of this email at <http://llvmweekly.org/issue/57>. Welcome to the fifty-seventh 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 Bradbury](http://asbradbury.org). Subscribe to future issues at <http://llvmweekly.org> and pass it on to anyone else you think may be interested. Please send any tips or feedback to <asb at asbradbury.org>, or @llvmweekly or @asbradbury on Twitter. I've been at FOSDEM this weekend in Brussels (which i...