All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <ak@muc.de>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Arjan van de Ven <arjan@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: -freg-struct-return?
Date: Thu, 22 Feb 2007 08:42:56 -0800	[thread overview]
Message-ID: <45DDC810.3000401@zytor.com> (raw)
In-Reply-To: <20070222112207.GA10190@muc.de>

Andi Kleen wrote:
> 
> I didn't think we had any that returned structures.
> 

Sometimes returning small structures is really nice.  If you can pass 
them in registers, it's often generates the fastest possible code; much 
better than using a pointer.

	-hpa

  reply	other threads:[~2007-02-22 16:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22  1:28 -freg-struct-return? Jeremy Fitzhardinge
2007-02-22  8:04 ` -freg-struct-return? Arjan van de Ven
2007-02-22  8:09   ` -freg-struct-return? Jeremy Fitzhardinge
2007-02-22  8:15     ` -freg-struct-return? Arjan van de Ven
2007-02-22  8:30       ` -freg-struct-return? Jeremy Fitzhardinge
2007-02-22  8:37       ` -freg-struct-return? Ingo Molnar
2007-02-22  8:38     ` [patch] x86: add -freg-struct-return to CFLAGS Ingo Molnar
2007-02-22 11:23       ` Andi Kleen
2007-02-22 11:27         ` Arjan van de Ven
2007-02-22 18:35       ` Adrian Bunk
2007-02-22 22:31         ` H. Peter Anvin
2007-02-22  9:50     ` -freg-struct-return? Jakub Jelinek
2007-02-22 11:22     ` -freg-struct-return? Andi Kleen
2007-02-22 16:42       ` H. Peter Anvin [this message]
2007-02-22 17:39         ` -freg-struct-return? Jeremy Fitzhardinge
2007-02-22 18:36           ` -freg-struct-return? Andi Kleen
2007-02-22 18:48             ` -freg-struct-return? H. Peter Anvin
2007-02-23  0:21               ` -freg-struct-return? Andi Kleen
2007-02-22 18:56             ` -freg-struct-return? Jan Engelhardt
2007-02-22 19:12               ` -freg-struct-return? H. Peter Anvin

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=45DDC810.3000401@zytor.com \
    --to=hpa@zytor.com \
    --cc=ak@muc.de \
    --cc=arjan@infradead.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.