[llvm-dev] [RFC] Queries for LLVM version

Nemanja Ivanovic via llvm-dev llvm-dev at lists.llvm.org
Tue Feb 7 15:12:19 PST 2017

I am certainly willing to write up a patch to do this. I was hoping to get
a few more responses/buy-in from the community.
And honestly, I'd be interested to know if this can be back-ported to at
least 4.0 if it gets accepted.

Now that I see that there's more interest in this than just my own, I'll
put up a patch on Phabricator.

On Wed, Feb 8, 2017 at 12:04 AM, Timothy Arceri via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> On 01/26/2017 12:45 AM, Nemanja Ivanovic via llvm-dev wrote:
> > This has actually come up in the context of a JIT, but I think that
> > having the functionality in general could be useful.
> >
> > Currently, there does not appear to be an API in LLVM to query for
> > LLVM version information. In the particular context where this came
> > up, LLVM is used as a shared library and various functionality (and
> > bug fixes) used by the JIT is available in various LLVM versions. So
> > it would be quite convenient to be able to dynamically determine the
> > version that happens to be loaded.
> >
> > Honestly, I am not completely clear on what the best place for
> > something like this would be, but it appears that the following
> seems
> > like a natural choice:
> >
> > llvm::VersionPrinter in lib/Support/CommandLine.cpp already queries
> > this data so it might make sense for it to expose the following
> API's
> > (as part of VersionPrinter, accessed through the instance):
> > llvm::cl::getVersionMajor()
> > llvm::cl::getVersionMinor()
> > llvm::cl::getVersionPatch()
> Hi,
> I'm also interested in querying this at runtime. Has there been any
> patches submitted for this yet?
> Thanks,
> Tim
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170208/08d164c7/attachment.html>

More information about the llvm-dev mailing list