public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz>
To: Jie Zhang <zhangjie@magima.com.cn>
Cc: Jan Hubicka <jh@suse.cz>,
	Nathan Sidwell <nathan@codesourcery.com>,
	gcc@gcc.gnu.org, Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
Subject: Re: [PATCH] Re: Option -fprofile-arcs fails for target avr and fr30
Date: Tue, 20 May 2003 09:24:00 -0000	[thread overview]
Message-ID: <20030520085747.GC1375@kam.mff.cuni.cz> (raw)
In-Reply-To: <3EC98E5A.7050008@magima.com.cn>

> 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?
Bacporting that patch I guess.  It should be safe.

Honza
> 
> - Jie
> 

  reply	other threads:[~2003-05-20  9:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16  9:53 Jie Zhang
2003-05-19  2:55 ` [PATCH] " Jie Zhang
2003-05-19  9:20   ` Nathan Sidwell
2003-05-19 14:25     ` Jan Hubicka
2003-05-20  2:59       ` Jie Zhang
2003-05-20  9:24         ` Jan Hubicka [this message]
2003-05-20  3:03       ` DJ Delorie
2003-05-19 16:38   ` Zdenek Dvorak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030520085747.GC1375@kam.mff.cuni.cz \
    --to=jh@suse.cz \
    --cc=gcc@gcc.gnu.org \
    --cc=nathan@codesourcery.com \
    --cc=rakdver@atrey.karlin.mff.cuni.cz \
    --cc=zhangjie@magima.com.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).