public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: "'Hans-Peter Nilsson'" <hans-peter.nilsson@axis.com>
Cc: <bonzini@gnu.org>, 	<gcc@gcc.gnu.org>
Subject: RE: How to stop gcc from not calling noinline functions
Date: Mon, 14 Jan 2008 15:01:00 -0000	[thread overview]
Message-ID: <031d01c856a7$7859d720$2e08a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <200801141143.m0EBh2SU019554@ignucius.se.axis.com>

On 14 January 2008 11:43, Hans-Peter Nilsson wrote:

>> From: "Dave Korn" <dave.korn@artimi.com>
>> Date: Mon, 14 Jan 2008 11:26:33 -0000
> 
>>   If you wanted to stick to standard C, you could surely force it with a
>> call through function pointer, perhaps?  (You might need to make it
>> volatile to fool IPA.)
> 
> No.  No tricks in the calling function.  To reiterate my main
> use: test-cases.  Changing from a direct function call in the
> original code to indirect is too much a difference, not to say a
> (pointer to) volatile.

  Oops, yes it is, I just re-read your original post; it's the caller, and the
call itself you care about, not what's in the (inlined-or-not) callee.
Apologies.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

  reply	other threads:[~2008-01-14 12:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-12  8:26 Hans-Peter Nilsson
2008-01-12  9:34 ` kai-gcc
2008-01-12 10:24 ` Paolo Bonzini
2008-01-14 11:26   ` Hans-Peter Nilsson
2008-01-14 11:36     ` Dave Korn
2008-01-14 11:43       ` Jan Hubicka
2008-01-14 12:18       ` Hans-Peter Nilsson
2008-01-14 15:01         ` Dave Korn [this message]
2008-01-12 11:34 ` Richard Guenther
2008-02-06 23:59   ` Mark Mitchell
2008-02-07  1:19     ` Hans-Peter Nilsson

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='031d01c856a7$7859d720$2e08a8c0@CAM.ARTIMI.COM' \
    --to=dave.korn@artimi.com \
    --cc=bonzini@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=hans-peter.nilsson@axis.com \
    /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).