From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15901 invoked by alias); 20 May 2003 02:09:29 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 15620 invoked from network); 20 May 2003 02:09:28 -0000 Received: from unknown (HELO www6.chinadns.com) (211.154.211.69) by sources.redhat.com with SMTP; 20 May 2003 02:09:28 -0000 Received: (qmail 13513 invoked from network); 20 May 2003 02:09:24 -0000 Received: from unknown (HELO magima.com.cn) (zhangjie@magima.com.cn@unknown) by unknown with SMTP; 20 May 2003 02:09:24 -0000 Message-ID: <3EC98E5A.7050008@magima.com.cn> Date: Tue, 20 May 2003 02:59:00 -0000 From: Jie Zhang User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507 X-Accept-Language: en-us, en, zh, ja MIME-Version: 1.0 To: Jan Hubicka CC: Nathan Sidwell , gcc@gcc.gnu.org, Zdenek Dvorak Subject: Re: [PATCH] Re: Option -fprofile-arcs fails for target avr and fr30 References: <3EC4B4D8.1040504@magima.com.cn> <3EC84136.6040705@magima.com.cn> <3EC89EDC.4000706@codesourcery.com> <20030519135752.GD15316@kam.mff.cuni.cz> In-Reply-To: <20030519135752.GD15316@kam.mff.cuni.cz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-05/txt/msg01827.txt.bz2 Jan Hubicka wrote: >There is code to set the JUMP_LABEL properly in the code to emit insn on >the edges: > insert_insn_on_edge (edge_profile, e); > rebuild_jump_labels (e->insns); >rebuild_jump_labels is supposed to update JUMP_LABEL accordingly. >In case the profiling code somewhere does not update labels correctly it >is the bug on place where code is emit. I will try to figure out what >happens tomorrow. At the time the basic blocks are split, all >JUMP_LABELs are supposed to be up-to-date. > >Honza > > > > Sorry, I didn't see that rebuild_jump_labels was added into HEAD of cvs on Mar 30, 2003, I'm only tracking 3.3 branch now, which had been branched before it was added. Now how do we fix this bug on 3.3 branch? - Jie