netdev - xmm registers in amd64 drivers

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>] [day] [month] [year] [list]

Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6026B734B@saturn3.aculab.com>
Date:	Thu, 19 Sep 2013 11:31:46 +0100
From:	"David Laight" <David.Laight@...LAB.COM>
To:	"Network Development" <netdev@...r.kernel.org>
Subject: xmm registers in amd64 drivers

I realise this isn't quite the right list for this question.
But I suspect someone will know the answer!

I've just compiled one of our drivers (an ss7 protocol stack)
on a much newer system than the one we usually use
(ubunto 13.04 with gcc 4.7.3 rather than debian lenny).

I've bodged around some strict-aliasing and const-cast warnings
- the usage all look safe.

Looking at the object code I noticed that all the stdarg
functions now contain code to conditionally save the xmm
registers.

Is this now considered 'normal' or am I missing a compiler flag?

I know I've looked at the code before since I tried adding
enough fixed parameters to one of the functions to get all
the variable ones on-stack hoping that would optimise the
accesses - it didn't.

	David

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html