public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/99785] Awful lot of time spent building gl.cc in Firefox Date: Wed, 31 Mar 2021 13:32:11 +0000 [thread overview] Message-ID: <bug-99785-4-XKNnCaRFBs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99785-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99785 --- Comment #17 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Jeff Muizelaar from comment #14) > re: __builtin_shuffle vs __builtin_shufflevector - It looks like > __builtin_shuffle doesn't support constructing vectors of a different size > than input type. That's mostly what we're using __builtin_shufflevector for. > __builtin_shufflevector > https://github.com/servo/webrender/blob/master/swgl/src/vector_type.h Indeed that's more powerful that __builtin_shuffle. It would map loosely as to what (vec_select (vec_concat ....) ...) on RTL can do but on GIMPLE we don't have a 1:1 match though I've thought of extending it this way at multiple occasions (by extending the existing VEC_PERM_EXPR, basically relaxing the set of valid operands/results). The complication of doing that is always that targets need to be made aware of the possibilities. At least internally I've also pondered allowing a scalar as input serving as single-element vector. > I briefly tried to get the gcc variant of the code compiling with clang but > ran into a number of issues including clang's lack of support for > '__builtin_shuffle'. If you'd like to try, the swgl code is pretty easy to > build locally if you. You should be able to just checkout > https://github.com/servo/webrender/ navigate to the the 'swgl' directory and > run 'cargo build --release' > > re: inlining huge functions - We tried not inlining blend_pixels with clang > and it seems to have a negative impact on a number of benchmarks. Did you report this as an issue to them? That is, leaving auto-inlining to clangs heuristic and those not working?
next prev parent reply other threads:[~2021-03-31 13:32 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-26 7:57 [Bug c++/99785] New: " mh+gcc at glandium dot org 2021-03-26 8:26 ` [Bug c++/99785] " pinskia at gcc dot gnu.org 2021-03-26 8:27 ` pinskia at gcc dot gnu.org 2021-03-26 8:29 ` pinskia at gcc dot gnu.org 2021-03-26 8:33 ` [Bug ipa/99785] " mh+gcc at glandium dot org 2021-03-26 8:41 ` pinskia at gcc dot gnu.org 2021-03-26 8:49 ` mh+gcc at glandium dot org 2021-03-26 9:08 ` mh+gcc at glandium dot org 2021-03-26 9:27 ` pinskia at gcc dot gnu.org 2021-03-26 9:29 ` jakub at gcc dot gnu.org 2021-03-26 9:33 ` rguenth at gcc dot gnu.org 2021-03-26 9:35 ` rguenth at gcc dot gnu.org 2021-03-26 10:11 ` rguenth at gcc dot gnu.org 2021-03-26 11:16 ` rguenth at gcc dot gnu.org 2021-03-26 19:31 ` jmuizelaar at mozilla dot com 2021-03-26 21:38 ` hubicka at gcc dot gnu.org 2021-03-26 22:13 ` hubicka at gcc dot gnu.org 2021-03-31 13:32 ` rguenth at gcc dot gnu.org [this message] 2021-03-31 13:37 ` jakub at gcc dot gnu.org 2021-05-21 7:29 ` rguenth at gcc dot gnu.org 2021-05-21 9:35 ` rguenth at gcc dot gnu.org 2022-05-17 11:26 ` asolokha at gmx dot com 2022-05-17 15:09 ` jmuizelaar at mozilla dot com
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=bug-99785-4-XKNnCaRFBs@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).