search for: d10725

Displaying 5 results from an estimated 5 matches for "d10725".

2015 Aug 17
2
[LLVMdev] [RFC] Developer Policy for LLVM C API
On Sun, Aug 16, 2015 at 6:45 PM deadal nix via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Chiming in with http://reviews.llvm.org/D10725 > > Being able to read and generate IR is at least some very basic thing we > can agree on is needed. Can we get some testing for it ? Personally I don't > really mind if this is going to be stable or not, but at least, having some > test coverage would allow to take whatever pat...
2015 Sep 06
2
LLVMBuildLandingPad is wrong on 3.7
...8facbc5c707c77f25f7fd9b512a099af62a8 . Alternatively, master can be made compatible with 3.7 . I'd like to add that having some actual testing for the C API would have prevented the whole confusion in the first place. I have a diff out to start moving in that direction: http://reviews.llvm.org/D10725 . The damn thing is out since June and nothing have moved since then. If core devs are swaped and can't handle this, please delegate. I know there is some discussion about the state of the C API, but the thread is dead for weeks now, reasonable options have been presented, and I'm not sure...
2015 Aug 17
3
[LLVMdev] [RFC] Developer Policy for LLVM C API
...l.com> wrote: > 2015-08-16 21:47 GMT-07:00 Eric Christopher <echristo at gmail.com>: > >> >> >> On Sun, Aug 16, 2015 at 6:45 PM deadal nix via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> Chiming in with http://reviews.llvm.org/D10725 >>> >>> Being able to read and generate IR is at least some very basic thing we >>> can agree on is needed. Can we get some testing for it ? Personally I don't >>> really mind if this is going to be stable or not, but at least, having some >>> test c...
2015 Jul 17
15
[LLVMdev] [RFC] Developer Policy for LLVM C API
Hi @ll, a few of us had recently a discussion about how to manage the C API and possible policies regarding addition, maintenance, deprecation, and removal of API. Even thought there is a strong agreement in the community that we shouldn't break released C API and should be backwards compatible, there doesn’t seem to be a developer policy that backs that up. This is something we should fix.
2015 Aug 17
6
[LLVMdev] [RFC] Developer Policy for LLVM C API
As someone who used the LLVM C API for an experiment back in 2009ish (porting the SBCL lisp compiler to target LLVM as a backend -- never finished), I thought it was great that LLVM provided the C API. I was sad that it wasn't properly updated to include support for all the newly introduced IR features, though. (E.g. atomics). I tried to send patches for some of that stuff a while later, but