linux-kernel - Re: [PATCH] trivial: the memset operation on a automatic array variable should be optimized out by data initialization

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: <1182723318.6819.5.camel@laptopd505.fenrus.org>
Date:	Sun, 24 Jun 2007 15:15:17 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Oleg Verych <olecom@...wer.upol.cz>
Cc:	rae l <crquan@...il.com>, trivial@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] trivial: the memset operation on a automatic array
	variable should be optimized out by data initialization


> > I think all these benefits are the gcc's __builtin_memset optimization
> > than the explicit call to memset.
> 
> ... or from complex memset() implementation (some chips even didn't do
> `rep' fast enough somehow). Maybe code like below will be acceptable for
> both optimizers and maintainers?


we should just alias our memset to the __builtin one, and then provide a
generic one from lib/ for the cases gcc needs to do a fallback.


-
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/