From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24719 invoked by alias); 20 Jun 2011 16:23:09 -0000 Received: (qmail 24711 invoked by uid 22791); 20 Jun 2011 16:23:08 -0000 X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from mo-p00-ob.rzone.de (HELO mo-p00-ob.rzone.de) (81.169.146.160) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 20 Jun 2011 16:22:45 +0000 X-RZG-AUTH: :LXoWVUeid/7A29J/hMvvT2k715jHQaJercGObUOFkj18odoYNahU4Q== X-RZG-CLASS-ID: mo00 Received: from [192.168.0.22] (business-188-111-022-002.static.arcor-ip.net [188.111.22.2]) by post.strato.de (jimi mo26) (RZmta 25.18) with ESMTPA id t01262n5KF9ove ; Mon, 20 Jun 2011 18:18:52 +0200 (MEST) Message-ID: <4DFF72EC.1040601@gjlay.de> Date: Mon, 20 Jun 2011 16:52:00 -0000 From: Georg-Johann Lay User-Agent: Thunderbird 2.0.0.24 (X11/20100302) MIME-Version: 1.0 To: Richard Henderson CC: "Joseph S. Myers" , gcc-patches@gcc.gnu.org, Denis Chertykov , Anatoly Sokolov , "Eric B. Weddington" Subject: Re: [Patch, AVR]: QI builtins for parity, popcount, 1<< n References: <4DFA26FE.1000400@gjlay.de> <4DFB32BA.9090009@gjlay.de> <4DFB9DD9.9070700@gjlay.de> <4DFF573D.2000807@gjlay.de> <4DFF6903.4060508@redhat.com> In-Reply-To: <4DFF6903.4060508@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2011-06/txt/msg01504.txt.bz2 Richard Henderson schrieb: > On 06/20/2011 07:20 AM, Georg-Johann Lay wrote: >> A libcall could be added in TARGET_INIT_LIBCALLS, so a new hook is not >> needed. All that's needed is that optabs tests for presence of such >> an entry and prefers it over inline expansion (and prefers insn over >> libcall). It appears that + and - are assumed to be cheaps or inline >> expansion is always cheap. > > No, we assume that if the inline pattern is present and enabled, it > is to be preferred over the libcall. All you have to do to get > __adddi3 called is remove/disable the adddi3 pattern. There is no adddi3 in avr backend to disable. -- Johann