From: David Malcolm <dmalcolm@redhat.com>
To: Andrea Corallo <andrea.corallo@arm.com>, gcc-patches@gcc.gnu.org
Cc: "jit@gcc.gnu.org" <jit@gcc.gnu.org>, nd <nd@arm.com>,
jakub@redhat.com, Richard Biener <rguenther@suse.de>
Subject: Re: [PATCH V3][gcc] libgccjit: introduce version entry points
Date: Fri, 20 Mar 2020 21:32:05 -0400 [thread overview]
Message-ID: <330ed10fb3e66abdbc5d30fdf2ba2fd3c3b30cf6.camel@redhat.com> (raw)
In-Reply-To: <gkrmu8d8efb.fsf@arm.com>
On Wed, 2020-03-18 at 23:51 +0100, Andrea Corallo wrote:
> Hi all,
>
> Updated version of the patch mainly addressing comments on the
> concurrency issues.
>
> I came to the conclusions that the caching should be done in the
> function that we decide to be thread safe. However I haven't touched
> parse_basever in any direction in the hope of having this still in
> stage4. As result I've mostly applied the mutex solution.
>
> 'make check-jit' runs clean
>
> Bests
>
> Andrea
>
> gcc/jit/ChangeLog
> 2020-??-?? Andrea Corallo <andrea.corallo@arm.com>
> David Malcolm <dmalcolm@redhat.com>
>
> * docs/topics/compatibility.rst (LIBGCCJIT_ABI_13): New ABI tag
> plus add version paragraph.
> * libgccjit++.h (namespace gccjit::version): Add new namespace.
> * libgccjit.c (gcc_jit_version_major, gcc_jit_version_minor)
> (gcc_jit_version_patchlevel): New functions.
> * libgccjit.h (LIBGCCJIT_HAVE_gcc_jit_version): New macro.
> (gcc_jit_version_major, gcc_jit_version_minor)
> (gcc_jit_version_patchlevel): New functions.
> * libgccjit.map (LIBGCCJIT_ABI_13) New ABI tag.
>
> gcc/testsuite/ChangeLog
> 2020-??-?? Andrea Corallo <andrea.corallo@arm.com>
>
> * jit.dg/test-version.c: New testcase.
> * jit.dg/all-non-failing-tests.h: Add test-version.c.
> diff --git a/gcc/testsuite/jit.dg/all-non-failing-tests.h b/gcc/testsuite/jit.dg/all-non-failing-tests.h
> index 0272e6f846f..cba4ac51cc9 100644
> --- a/gcc/testsuite/jit.dg/all-non-failing-tests.h
> +++ b/gcc/testsuite/jit.dg/all-non-failing-tests.h
> @@ -8,6 +8,13 @@
> hooks provided by each test case. */
> #define COMBINED_TEST
>
> +/* test-version.c */
> +#define create_code create_code_version
> +#define verify_code verify_code_version
> +#include "test-version.c"
> +#undef create_code
> +#undef verify_code
> +
> /* test-accessing-bitfield.c */
> #define create_code create_code_accessing_bitfield
> #define verify_code verify_code_accessing_bitfield
Please add the new test to the header in its alphabetical location,
i.e. between:
/* test-vector-types.cc: We don't use this, since it's C++. */
and
/* test-volatile.c */
An entry also needs to be added to the "testcases" array at the end of
the header (again, in the alphabetical-sorted location).
OK by me with that change (assuming you re-test the patch), but given
we're in stage 4, it's probably worth double-checking with a release
manager. I've CCed Jakub and Richi.
Dave
next prev parent reply other threads:[~2020-03-21 1:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 0:00 [PATCH][gcc] " Andrea Corallo
2020-01-01 0:00 ` David Malcolm
2020-01-01 0:00 ` Florian Weimer
2020-01-01 0:00 ` Andrea Corallo
2020-01-01 0:00 ` David Malcolm
2020-03-08 14:08 ` Andrea Corallo
2020-03-18 22:51 ` [PATCH V3][gcc] " Andrea Corallo
2020-03-21 1:32 ` David Malcolm [this message]
2020-03-23 13:03 ` Richard Biener
2020-03-29 20:31 ` Andrea Corallo
2020-03-30 16:09 ` David Malcolm
2020-03-31 1:13 ` David Malcolm
2020-03-31 8:03 ` Andrea Corallo
2020-03-31 12:05 ` [PATCH V4][gcc] " Andrea Corallo
2020-03-31 17:33 ` David Malcolm
2020-03-31 19:00 ` Andrea Corallo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=330ed10fb3e66abdbc5d30fdf2ba2fd3c3b30cf6.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=andrea.corallo@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jit@gcc.gnu.org \
--cc=nd@arm.com \
--cc=rguenther@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).