On Mon, Jun 22, 2020 at 03:14:44PM -0400, y2s1982 . via Gcc wrote:
> > > If the 4 separate bytes of the version isn't something written somewhere
> > in
> > > the standard, I'd use something along the lines of
> > > #define GCC_VERSION (__GNUC__ * 1000 + __GNUC_MINOR__)
> > > macro, so make it
> >
On Mon, Jun 22, 2020 at 1:54 PM Jeffrey Walton via Gcc
wrote:
> On Mon, Jun 22, 2020 at 1:47 PM Jakub Jelinek via Gcc
> wrote:
> >
> > On Sat, Jun 20, 2020 at 01:26:59PM -0400, y2s1982 . via Gcc wrote:
> > > I have a question on API version formatting.
> > > I have been looking at the get_api_ve
On Mon, Jun 22, 2020 at 1:47 PM Jakub Jelinek via Gcc wrote:
>
> On Sat, Jun 20, 2020 at 01:26:59PM -0400, y2s1982 . via Gcc wrote:
> > I have a question on API version formatting.
> > I have been looking at the get_api_version() and get_api_version_string()
> > documentation:
> > https://www.open
On Sat, Jun 20, 2020 at 01:26:59PM -0400, y2s1982 . via Gcc wrote:
> I have a question on API version formatting.
> I have been looking at the get_api_version() and get_api_version_string()
> documentation:
> https://www.openmp.org/spec-html/5.0/openmpsu213.html#x269-17920005.5.1.2
> I also saw how
Hello,
I have a question on API version formatting.
I have been looking at the get_api_version() and get_api_version_string()
documentation:
https://www.openmp.org/spec-html/5.0/openmpsu213.html#x269-17920005.5.1.2
I also saw how LLVM implements it using macro to store the information:
https://git
