public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joerg.richter@pdv-fs.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59739] New: missed optimization: attribute ((pure)) could be honored more often Date: Thu, 09 Jan 2014 16:43:00 -0000 [thread overview] Message-ID: <bug-59739-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59739 Bug ID: 59739 Summary: missed optimization: attribute ((pure)) could be honored more often Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: joerg.richter@pdv-fs.de Created attachment 31786 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31786&action=edit Script for demonstration Attached is a script (t.sh) that creates two .cc files, compiles and executes them. It tests whether attribute ((pure)) is used on different functions with this signatures: struct Struct { int val; }; int globalInt(); Struct globalStruct(); struct Class { int classInt(); Struct classStruct(); virtual int classVirtualInt(); virtual Struct classVirtualStruct(); }; The output with GCC is 4.8.2 is this: globalInt: 1 globalStruct: 0 classInt: 1 classStruct: 0 classVirtualInt: 0 classVirtualStruct: 0 Meaning only globalInt and classInt are optimised. All other functions are also candidates for attribute-pure optimisation.
next reply other threads:[~2014-01-09 16:43 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-09 16:43 joerg.richter@pdv-fs.de [this message] 2014-01-15 16:16 ` [Bug c++/59739] " joerg.richter@pdv-fs.de 2015-03-19 9:19 ` paolo.carlini at oracle dot com 2015-03-19 22:11 ` hubicka at gcc dot gnu.org 2015-03-20 10:58 ` [Bug c++/59739] missed optimization: attribute ((pure)) with aggregate returns rguenth at gcc dot gnu.org 2021-12-20 20:28 ` pinskia at gcc dot gnu.org 2024-04-09 7:06 ` pinskia at gcc dot gnu.org 2024-04-09 7:07 ` pinskia 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-59739-4@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).