From: Kirill Yukhin <kirill.yukhin@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Uros Bizjak <ubizjak@gmail.com>,
Richard Henderson <rth@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH i386 AVX512] [81/n] Add new built-ins.
Date: Tue, 21 Oct 2014 14:52:00 -0000 [thread overview]
Message-ID: <20141021144749.GC22695@msticlxl57.ims.intel.com> (raw)
In-Reply-To: <20141021142015.GY10376@tucnak.redhat.com>
On 21 Oct 16:20, Jakub Jelinek wrote:
> On Tue, Oct 21, 2014 at 06:08:15PM +0400, Kirill Yukhin wrote:
> > --- a/gcc/tree.h
> > +++ b/gcc/tree.h
> > @@ -2334,6 +2334,10 @@ extern void decl_value_expr_insert (tree, tree);
> > #define DECL_COMDAT(NODE) \
> > (DECL_WITH_VIS_CHECK (NODE)->decl_with_vis.comdat_flag)
> >
> > + /* In a FUNCTION_DECL indicates that a static chain is needed. */
> > +#define DECL_STATIC_CHAIN(NODE) \
> > + (DECL_WITH_VIS_CHECK (NODE)->decl_with_vis.regdecl_flag)
> > +
>
> I would say that you should still keep it together with the FUNCTION_DECL
> macros and use FUNCTION_DECL_CHECK there, to make it clear we don't want
> the macro to be used on VAR_DECLs etc.
> So just s/function_decl/decl_with_vis/ in the definition IMHO.
Yeah, sure.
> Also, with so many added builtins, how does it affect
> int i;
> compilation time at -O0? If it is significant, maybe it is highest time to
> make the md builtin decl building more lazy.
I've tried this:
$ echo "int i;" > test.c
$ time for i in `seq 10000` ; do ./build-x86_64-linux/gcc/xgcc -B./build-x86_64-linux/gcc -O0 -S test.c ; done
For trunk w/ and w/o the patch applied.
Got 106.86 vs. 106.85 secs. which looks equal.
So, I think we may say that this patch does not affect compile time.
--
Thanks, K
>
> Jakub
next prev parent reply other threads:[~2014-10-21 14:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 13:50 Kirill Yukhin
2014-10-20 13:56 ` Jakub Jelinek
2014-10-21 9:19 ` Richard Biener
2014-10-21 14:19 ` Kirill Yukhin
2014-10-21 14:09 ` Kirill Yukhin
2014-10-21 14:21 ` Jakub Jelinek
2014-10-21 14:52 ` Kirill Yukhin [this message]
2014-10-21 15:13 ` Kirill Yukhin
2014-10-22 8:18 ` Richard Biener
2014-10-22 11:40 ` Kirill Yukhin
2014-10-22 11:43 ` Jakub Jelinek
2014-10-22 7:57 ` [PATCH AVX512] [81.1/n] Extend `function_code' field in `tree_var_decl' structure Kirill Yukhin
2014-10-23 11:10 ` Jakub Jelinek
2014-10-21 14:24 ` [PATCH i386 AVX512] [81/n] Add new built-ins Richard Biener
2014-10-23 12:58 ` [PATCH i386 AVX512] [81.2/n] " Kirill Yukhin
2014-10-23 13:46 ` Uros Bizjak
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=20141021144749.GC22695@msticlxl57.ims.intel.com \
--to=kirill.yukhin@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rth@redhat.com \
--cc=ubizjak@gmail.com \
/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).