search for: gravitas

...> I think it’s harmful to LLVM in the long run if external embedders use the C++ API. I think that one way of ensuring that they don’t have an excuse to do it is to flesh out some things: > > - Add more tests of the C API to ensure that people don’t break it accidentally and to give more gravitas to the C API backwards compatibility claims. > - Increase C API coverage. > - For example, WebKit currently sidesteps the C API to pass some commandline options to LLVM. We don’t want that. > - Add more support for reasoning about targets and triples. WebKit still has to...

...’s harmful to LLVM in the long run if external embedders use the C++ API. I think that one way of ensuring that they don’t have an excuse to do it is to flesh out some things: >>> >>> - Add more tests of the C API to ensure that people don’t break it accidentally and to give more gravitas to the C API backwards compatibility claims. >>> - Increase C API coverage. >>> - For example, WebKit currently sidesteps the C API to pass some commandline options to LLVM. We don’t want that. >>> - Add more support for reasoning about targets and triples....

...t’s harmful to LLVM in the long run if external embedders use the > C++ API. I think that one way of ensuring that they don’t have an excuse to > do it is to flesh out some things: > > - Add more tests of the C API to ensure that people don’t break it > accidentally and to give more gravitas to the C API backwards compatibility > claims. > - Increase C API coverage. > - For example, WebKit currently sidesteps the C API to pass some > commandline options to LLVM. We don’t want that. > - Add more support for reasoning about targets and triples. WebKit > st...

Hello LLVM community, Over the last few years the LLVM team here at Apple and development teams elsewhere have been busily working on finding new and interesting uses for LLVM. Some of these uses are traditional compilers, but a growing number of them aren’t. Some of LLVM’s new clients, like WebKit, are embedding LLVM into existing applications. These embedded uses of LLVM have their own unique

...an albatross to be suffered. There is work necessary to change that perception too. I think that one way of ensuring that they don’t have an excuse to do it is to flesh out some things: > > - Add more tests of the C API to ensure that people don’t break it accidentally and to give more gravitas to the C API backwards compatibility claims. Yes, for well-designed high level APIs like libLTO and libIndex. For other APIs, we should remove the backwards compatibility guarantees ... > - Increase C API coverage. ... which in turn allows us to do this. Designing a good high-level API is h...