public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jie Zhang <zhangjie@magima.com.cn>
To: gcc@gcc.gnu.org
Subject: Option -fprofile-arcs fails for target avr and fr30
Date: Fri, 16 May 2003 09:53:00 -0000	[thread overview]
Message-ID: <3EC4B4D8.1040504@magima.com.cn> (raw)

Hi, I have a question about using -fprofile-arcs option on avr and fr30 
targets for gcc-3.3.

Avr and fr30 targets have no DI mode add instructions, nor add with 
carry instructions. But profile instrument code needs DI mode add. GCC 
has to translate the DImode add into a sequence of instructions. That 
will introduce new jump_insn, which will cause make_edges abort. Testing 
gcc.misc-tests/bprob-1.c reveals this problem.

I think GCC should take this case into acount. But I have no good method 
by now. Does anyone have good solution? Thanks!

- J


             reply	other threads:[~2003-05-16  9:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16  9:53 Jie Zhang [this message]
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
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=3EC4B4D8.1040504@magima.com.cn \
    --to=zhangjie@magima.com.cn \
    --cc=gcc@gcc.gnu.org \
    /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).