public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/47000] [4.5 Regression] Failure to inline SSE intrinsics Date: Sat, 18 Dec 2010 20:26:00 -0000 [thread overview] Message-ID: <bug-47000-4-HPgjnVgPW9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47000-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47000 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-12-18 20:26:29 UTC --- I don't think it is a good idea to change inliner heuristics in 4.5 at this point. If it is always a good idea to inline that function, it should be __attribute__((always_inline)).
next prev parent reply other threads:[~2010-12-18 20:26 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-18 7:46 [Bug c/47000] New: Major performance regression in parallel SSE2 impl of SHA256 hash algorithm jgarzik at pobox dot com 2010-12-18 7:48 ` [Bug c/47000] " jgarzik at pobox dot com 2010-12-18 12:27 ` [Bug target/47000] " steven at gcc dot gnu.org 2010-12-18 12:39 ` steven at gcc dot gnu.org 2010-12-18 12:49 ` steven at gcc dot gnu.org 2010-12-18 15:36 ` hjl.tools at gmail dot com 2010-12-18 15:41 ` hjl.tools at gmail dot com 2010-12-18 15:43 ` hjl.tools at gmail dot com 2010-12-18 16:04 ` hjl.tools at gmail dot com 2010-12-18 18:24 ` jgarzik at pobox dot com 2010-12-18 18:49 ` jgarzik at pobox dot com 2010-12-18 19:08 ` jgarzik at pobox dot com 2010-12-18 19:09 ` jgarzik at pobox dot com 2010-12-18 19:21 ` steven at gcc dot gnu.org 2010-12-18 19:35 ` [Bug target/47000] [4.5 Regression] Failure to inline SSE intrinsics hjl.tools at gmail dot com 2010-12-18 19:39 ` hjl.tools at gmail dot com 2010-12-18 20:26 ` jakub at gcc dot gnu.org [this message] 2010-12-18 21:15 ` jgarzik at pobox dot com 2010-12-18 21:16 ` jgarzik at pobox dot com 2010-12-18 21:17 ` jgarzik at pobox dot com 2010-12-18 21:26 ` jgarzik at pobox dot com 2010-12-19 11:50 ` hubicka at ucw dot cz 2010-12-19 11:53 ` hubicka at gcc dot gnu.org 2010-12-19 11:58 ` hubicka at gcc dot gnu.org 2010-12-20 8:32 ` jakub at gcc dot gnu.org 2010-12-21 10:31 ` hubicka at gcc dot gnu.org 2010-12-21 10:39 ` hubicka at gcc dot gnu.org 2010-12-28 14:57 ` rguenth at gcc dot gnu.org 2011-03-08 13:20 ` rguenth at gcc dot gnu.org 2011-04-28 15:28 ` rguenth at gcc dot gnu.org 2012-07-02 10:28 ` rguenth at gcc dot gnu.org
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-47000-4-HPgjnVgPW9@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).