public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/101064] long compile time in var_tracking for Go package Date: Tue, 29 Jun 2021 18:01:28 +0000 [thread overview] Message-ID: <bug-101064-4-6yvWFzkOun@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101064-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101064 --- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Ian Lance Taylor <ian@gcc.gnu.org>: https://gcc.gnu.org/g:8a8a7d332d5d01db5aea7336a36d9fd71a679fb1 commit r12-1913-g8a8a7d332d5d01db5aea7336a36d9fd71a679fb1 Author: Ian Lance Taylor <iant@golang.org> Date: Mon Jun 28 16:47:55 2021 -0700 compiler: in composite literals use temps only for interfaces For a composite literal we only need to introduce a temporary variable if we may be converting to an interface type, so only do it then. This saves over 80% of compilation time when using gccgo to compile cmd/internal/obj/x86, as the GCC middle-end spends a lot of time pointlessly computing interactions between temporary variables. For PR debug/101064 For golang/go#46600 Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/331513
next prev parent reply other threads:[~2021-06-29 18:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-14 13:01 [Bug debug/101064] New: " thanm at google dot com 2021-06-29 18:01 ` cvs-commit at gcc dot gnu.org [this message] 2021-06-29 18:01 ` [Bug debug/101064] " cvs-commit at gcc dot gnu.org 2021-06-29 18:54 ` ian at airs dot com 2021-06-29 18:56 ` ian at airs dot com 2021-06-29 19:00 ` ian at airs 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-101064-4-6yvWFzkOun@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).