Subject: Re: [PATCH] trivial: the memset operation on a automatic array
	variable should be optimized out by data initialization
From: Arjan van de Ven <arjan@infradead.org>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: rae l <crquan@gmail.com>, trivial@kernel.org, linux-kernel@vger.kernel.org
In-Reply-To: <20070624222518.GA10398@flower.upol.cz>
References: <467cac85.081b600a.5b88.457f@mx.google.com>
	 <E1I20Wr-00064i-T0@flower>
	 <91b13c310706240558p70dbaed2g570b57ab480aa974@mail.gmail.com>
	 <20070624222518.GA10398@flower.upol.cz>
Content-Type: text/plain
Organization: Intel International BV
Date: Sun, 24 Jun 2007 15:15:17 -0700
Message-Id: <1182723318.6819.5.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 685
Lines: 18


> > 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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/