public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/45273] [9/10/11/12 Regression] The compiler depends on the host double (-fprofile-corection only) Date: Thu, 06 Jan 2022 11:52:21 +0000 [thread overview] Message-ID: <bug-45273-4-7NCYDZve86@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-45273-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45273 Jan Hubicka <hubicka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hubicka at gcc dot gnu.org --- Comment #23 from Jan Hubicka <hubicka at gcc dot gnu.org> --- Note that with the introduction of profile-count.h I chased away most of uses of double for profile calculation. In predict.c we have last occurence when combinindg probabilities from predictors: combined_probability = (((double) combined_probability) * probability * REG_BR_PROB_BASE / d + 0.5); These are still REG_BR_PROB_BASE based (unlike rest of code that uses profile_probability datatype) since that was easier to have in .def file. Cast to double is there only to get type wide enough for REG_BR_PROB_BASE third power in the 32bit x86 era. It is set to 10000 that is roughly 2^14 so 43 bits (with sign bits) is enough that should be good for all reasonable double implementations. However we could easily change it to int64_t.
next prev parent reply other threads:[~2022-01-06 11:52 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-45273-4@http.gcc.gnu.org/bugzilla/> 2010-10-01 11:54 ` [Bug middle-end/45273] [4.4/4.5/4.6 " jakub at gcc dot gnu.org 2011-03-13 0:32 ` steven at gcc dot gnu.org 2011-03-13 10:55 ` steven at gcc dot gnu.org 2011-03-13 12:39 ` steven at gcc dot gnu.org 2011-04-16 10:52 ` [Bug middle-end/45273] [4.4/4.5/4.6/4.7 " jakub at gcc dot gnu.org 2012-01-20 13:17 ` rguenth at gcc dot gnu.org 2012-01-20 19:40 ` stevenb.gcc at gmail dot com 2013-03-22 14:44 ` [Bug middle-end/45273] [4.6/4.7/4.8/4.9 " jakub at gcc dot gnu.org 2013-05-31 10:58 ` [Bug middle-end/45273] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2013-10-16 9:48 ` jakub at gcc dot gnu.org 2014-05-22 9:04 ` [Bug middle-end/45273] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:35 ` [Bug middle-end/45273] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-06-23 8:18 ` [Bug middle-end/45273] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 20:04 ` [Bug middle-end/45273] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:34 ` jakub at gcc dot gnu.org 2021-05-14 9:46 ` [Bug middle-end/45273] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:04 ` rguenth at gcc dot gnu.org 2022-01-06 11:52 ` hubicka at gcc dot gnu.org [this message] 2022-05-27 9:34 ` [Bug middle-end/45273] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:29 ` jakub at gcc dot gnu.org 2023-07-07 10:29 ` [Bug middle-end/45273] [11/12/13/14 " 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-45273-4-7NCYDZve86@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).