public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45115] pure functions returning structs are not optimized.
Date: Wed, 28 Jul 2010 19:48:00 -0000	[thread overview]
Message-ID: <20100728194804.22993.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45115-3116@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from pinskia at gcc dot gnu dot org  2010-07-28 19:48 -------
Confirmed.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
             Status|UNCONFIRMED                 |NEW
          Component|c                           |tree-optimization
     Ever Confirmed|0                           |1
   GCC host triplet|x86_64-linux-gnu            |
           Keywords|                            |missed-optimization
   Last reconfirmed|0000-00-00 00:00:00         |2010-07-28 19:48:03
               date|                            |
            Summary|attribute((pure)) does not  |pure functions returning
                   |work when returning structs |structs are not optimized.


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45115


  reply	other threads:[~2010-07-28 19:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 19:45 [Bug c/45115] New: attribute((pure)) does not work when returning structs marco at technoboredom dot net
2010-07-28 19:48 ` pinskia at gcc dot gnu dot org [this message]
2010-07-28 20:05 ` [Bug tree-optimization/45115] pure functions returning structs are not optimized rguenth at gcc dot gnu dot org
     [not found] <bug-45115-4@http.gcc.gnu.org/bugzilla/>
2023-02-02  9:43 ` pinskia at gcc dot gnu.org
2023-02-02 10:15 ` redi at gcc dot gnu.org
2024-04-09  7:06 ` 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=20100728194804.22993.qmail@sourceware.org \
    --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: link
Be 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).