similar to: LLVM Cauldron 2016 (Sep 8th, Hebden Bridge, UK) registration and call for papers now open

Displaying 20 results from an estimated 1000 matches similar to: "LLVM Cauldron 2016 (Sep 8th, Hebden Bridge, UK) registration and call for papers now open"

2016 Aug 20
2
Cambridge LLVM Social, Sep 6th
The next Cambridge Social will be pushed a bit further into September, because of the holidays and the LLVM Cauldron. It'd be nice to welcome international LLVMers on the cauldron week. But that also forces the day of the week to be on a Tuesday. With the Cauldron in Hebden Bridge, people will be traveling on Wednesday evening and there would be no point in holding the social then. So, the
2016 Aug 18
8
[RFC] AAP Backend
Hi all, We wish to submit our latest AAP implementation as an experimental backend into LLVM. We need community feedback and reviewers for patches which we will submit soon. AAP was designed in early 2015 and aims to advance compiler development for small deeply embedded Harvard architectures, which are widely used commercially. AAP is freely available as an open source softcore for use in FPGA
2016 Nov 16
2
[RFC] AAP Backend
Hi all, I have just updated most of the patches to roll them forwards to LLVM top-of-tree, and incorporated various suggested changes. We're still looking for reviewers, if anyone is interested. Thank you, Edward Jones On 15/09/16 17:12, Ed Jones wrote: > I have now posted the final two patches for the backend to add > Disassembler support, ISel and CodeGen. The full list of patches
2016 Aug 25
2
[RFC] AAP Backend
As it stands, the active customers for this target are the out-of-tree backends which we are working on which can't be submitted for inclusion into LLVM. The general aim of the backend though is to include features from architectures which are not well represented in LLVM, for example non-power of two register sizes, non-octet chars, or very constrained register sets, and to this end we hope
2015 Dec 12
2
Some patches from mageia
Gene Cumm wrote: > On Sat, Dec 12, 2015 at 8:21 AM, Ady via Syslinux <syslinux at zytor.com> wrote: > > > >> On Thu, Dec 10, 2015 at 5:15 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: > >> > Gene Cumm wrote: > >> >> On Tue, Dec 1, 2015 at 3:02 PM, Erwan Velu via Syslinux > >> >> <syslinux at zytor.com> wrote: >
2015 Dec 12
2
Some patches from mageia
Gene Cumm wrote: > On Thu, Dec 10, 2015 at 5:15 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: > > Gene Cumm wrote: > >> On Tue, Dec 1, 2015 at 3:02 PM, Erwan Velu via Syslinux > >> <syslinux at zytor.com> wrote: > >> > Hi folks, > >> > > >> > As per Ady request (thanks for the reminder), I forgot to send the patches >
2015 Dec 12
2
Some patches from mageia
> On Thu, Dec 10, 2015 at 5:15 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: > > Gene Cumm wrote: > >> On Tue, Dec 1, 2015 at 3:02 PM, Erwan Velu via Syslinux > >> <syslinux at zytor.com> wrote: > >> > Hi folks, > >> > > >> > As per Ady request (thanks for the reminder), I forgot to send the patches > >> > I
2014 Aug 30
4
[LLVMdev] LLVM+GCC collaboration BoF
Folks, Is there any interest in having a BoF session on the GCC+LLVM collaboration? I'd like to discuss some of the outcomes from the GNU Cauldron session and see what we could do to make that relationship healthier. So far, all the cross discussions I've seen on the GNU list (about LLVM) have been very healthy and the GNU folks seem very receptive to discussion (not so much for
2016 Sep 13
3
https://reviews.llvm.org/D23393
On 9/12/16 11:40 PM, Davide Italiano wrote: > On Mon, Sep 12, 2016 at 10:03 PM, Alfred Perlstein via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hey folks, >> >> I'm new here, wasn't expecting to subscribe but here I am. The reason I'm >> here is that I came across a doc bug, I spent quite a bit of time learning >> all the tips and
2016 Nov 01
8
RFC: Improving the experience of first-time contributors
Hi all, Some discussions the night before prompted me to do a short lightning talk on 'improving the experience of first-time contributors' 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.
2020 Feb 28
2
Multi-Threading Compilers
Greetings All, For the last few months since the GCC Cauldron I've been researching/helping out plan for multi-threading GCC. I've posted my GCC ideas here: https://docs.google.com/document/d/1po_RRgSCtRyYgMHjV0itW8iOzJXpTdHYIpC9gUMjOxk/edit as I've heard there is interest on the LLVM side as well. I've talked to some of the IBM folks from the Toronto area about it face to face
2004 Feb 08
1
one-line fix reduces distortion
Ok maybe it's just my imagination, but it looks like the one-line "duh" fix I committed from Andrej Vakrcka <ander@cauldron.sk> this week DRAMATICALLY reduces distortion in encoded files. Take a look and compair. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to
2014 Dec 22
0
check-gnu-efi.sh: print the output of build-gnu-efi.sh
> I really think we should not take chances; > Syslinux source should include (probably as an optional download tarball) > the gnu-efi used to build the particular Syslinux version. > > apt-get is awesome but after running > LANG=C apt-get source syslinux > on my Ubuntu 14.04 I just got Syslinux 4.05 > The sources of a package like syslinux should not depend on >
2016 Sep 13
2
https://reviews.llvm.org/D23393
On 13 September 2016 at 07:59, Piotr Padlewski via llvm-dev <llvm-dev at lists.llvm.org> wrote: > This is exactly why we should switch to github. It is much easier for new > contributors to start with small fixes. There are two really quite separate issues here: 1) Patches, even trivial ones can sit unreviewed for long periods of time leading to a negative first time contribution
2014 Oct 08
3
[LLVMdev] More ARM asan failures - Line number
On 7 October 2014 20:55, Evgeniy Stepanov <eugenis at google.com> wrote: > Can you elaborate on this? Does it ever clean those lines? These > numbers are correct on multiple other platforms. I wonder if it's some > codegen peculiarity that leads to this off-by-one mistake? Can you go > down to the individual compile/run invocation and verify that line > numbers match (or
2013 Apr 03
14
ocaml bindings
i''m the Mageia Xen package maintainer, and a user reported that i had missing symbols in my ocaml bindings: https://bugs.mageia.org/show_bug.cgi?id=5199 i''m using Xen 4.2.1 and ocaml 3.12.1 the problem is that if you just to a simple hello world and you''re using certain bindings (eg: xeneventch): you get missing symbols. (others appear to be fine). I know next to
2015 Dec 10
3
Some patches from mageia
Gene Cumm wrote: > On Tue, Dec 1, 2015 at 3:02 PM, Erwan Velu via Syslinux > <syslinux at zytor.com> wrote: > > Hi folks, > > > > As per Ady request (thanks for the reminder), I forgot to send the patches > > I run in Mageia. > > > > There is two of them : > > > > One is making errors in parsing modules.alias not fatal. > > >
2018 Jun 04
4
chrony configuration for secondary samba DC
On Mon, 04 Jun 2018 04:59:55 +0200 Andrew Bartlett <abartlet at samba.org> wrote: > Perhaps when everyone has cooled down a little we can get the Samba > wiki page updated with this information? Sorry, but no, I don't think this is a good idea (yet), most distros do not have a new enough version of chrony for it to work. Put it on the Samba wiki that you can use chrony instead of
2015 Sep 16
2
[PATCH 0/4] efi: Makefile improvement
On mageia I'm using the following patch https://svnweb.mageia.org/packages/cauldron/syslinux/current/SOURCES/syslinux-nogit.patch?revision=600959&view=markup If it does solve your issue to, I could try pushing it into the repo. 2015-09-16 8:44 GMT+02:00 Thomas Letan via Syslinux <syslinux at zytor.com>: > Hi. > > Sometimes, it may happen that we do not want to clone a
2014 Jul 28
2
[LLVMdev] GCC and LLVM collaboration: Cauldron's feedback
Folks, As most of you know, I held a BoF at the cauldron where we discussed the interactions between LLVM and GCC, and the overall response was very positive. Here are some of the highlights, complementing Alex's great summary on the blog. 1. Driver ======= This was probably the most contentious issue. Compiler drivers are complex pieces of spaghetti code and each target's