linux-kernel - Re: -freg-struct-return?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1172131463.3531.226.camel@laptopd505.fenrus.org>
Date:	Thu, 22 Feb 2007 09:04:23 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Andi Kleen <ak@....de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: -freg-struct-return?

On Wed, 2007-02-21 at 17:28 -0800, Jeremy Fitzhardinge wrote:
> We have a number of functions which return small structures (such as
> pte_t).  It seems that the kernel is not compiled with
> -freg-struct-return, so all these small structures are being returned
> via the stack, even though they would fit into registers.
> 
> Is there a reason for this?  Would -freg-struct-return be preferred?  It
> would make a good compliment to -mregparm.

Do we know how many gcc bugs this has? (regparm used to have many)
other than that.. sounds like a win...

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/