public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Andrew Haley <aph@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Release novops attribute for external use?
Date: Mon, 12 Apr 2010 18:05:00 -0000	[thread overview]
Message-ID: <4BC364D4.8080907@gmail.com> (raw)
In-Reply-To: <4BC34B67.8090008@redhat.com>

On 12/04/2010 17:33, Andrew Haley wrote:
> On 04/12/2010 05:27 PM, Bingfeng Mei wrote:
>> Hello,
>> One of our engineers requested a feature so that
>> compiler can avoid to re-load variables after a function
>> call if it is known not to write to memory. It should 
>> slash considerable code size in our applications. I found
>> the existing "pure" and "const" cannot meet his requirements
>> because the function is optimized out if it doesn't return
>> a value.
> 
> If a function doesn't write to memory and it doesn't return a
> value, what is the point of calling it?

  Delay-loop!  That's about the only thing I can think of anyway :-)

    cheers,
      DaveK

  reply	other threads:[~2010-04-12 18:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 16:56 Bingfeng Mei
2010-04-12 16:58 ` Andrew Haley
2010-04-12 18:05   ` Dave Korn [this message]
2010-04-12 18:10     ` Andrew Haley
2010-04-12 18:29       ` Dave Korn
2010-04-12 20:53         ` Daniel Jacobowitz
2010-04-13  9:45   ` Bingfeng Mei
2010-04-13  9:56     ` Richard Guenther
2010-04-13 10:15       ` Andrew Haley
2010-04-13 10:23       ` Bingfeng Mei
2010-04-13 10:25         ` Richard Guenther
2010-04-13 10:57           ` Richard Guenther
2010-04-13 11:35             ` Bingfeng Mei
2010-04-13 11:53           ` Manuel López-Ibáñez
2010-04-13 15:06             ` Richard Guenther

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=4BC364D4.8080907@gmail.com \
    --to=dave.korn.cygwin@googlemail.com \
    --cc=aph@redhat.com \
    --cc=gcc@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).