From: Michael Matz <matz@suse.de>
To: kripa shankar <kripa82@yahoo.com>
Cc: gcc@gnu.org, gcc-help@gcc.gnu.org, crossgcc@sources.redhat.com
Subject: Re: your mail
Date: Mon, 23 Feb 2004 16:42:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0402231733260.20969@wotan.suse.de> (raw)
In-Reply-To: <20040223154755.23916.qmail@web41606.mail.yahoo.com>
Hi,
On Mon, 23 Feb 2004, kripa shankar wrote:
> ;; Start of basic block 2, registers live: 11 [fp] 13 [sp]
> (note 62 41 45 [bb 2] NOTE_INSN_BASIC_BLOCK)
> (insn 45 62 46 (set (reg/i:SI 0 r0) (const_int 0 [0x0])) 176 {*movsi_insn} (nil) (expr_list:REG_EQUAL (const_int 0 [0x0]) (nil)))
> (insn 46 45 76 (use (reg/i:SI 0 r0)) -1 (insn_list 45 (nil)) (nil))
> (insn 76 46 77 (set (reg:SI 7 r7) (plus:SI (reg:SI 5 r5) (const_int 2 [0x2]))) -1 (nil) (nil))
> (insn 77 76 50 (set (reg:SI 6 r6) (plus:SI (reg:SI 4 r4) (const_int 2 [0x2]))) -1 (nil) (nil))
> ;; End of basic block 2
> (note 50 77 63 0 NOTE_INSN_BLOCK_END)
> (note 63 50 0 "" NOTE_INSN_DELETED)
>
> The instructions inserted are r7 = r5 + 2;r6 = r4 + 2; But the problem
> is that the inserted instructions are not present in both asm file
> (fourth.s) and the output binary file (fourth.o).. I have inserted these
> instructions right after all the optimization passess and before the
> final pass (final.c) where RTL gets converted into Assembly. Kindly help
> me.
There is not enough information. Where exactly have you added the code to
add those insns? About which compiler version do you speak? Produce all
dump files (-da) and look which dump misses them first. The problem is,
that you include those instructions without updating lifeness (i.e. the
compiler doesn't see, that r6 and r7 really are required after you've set
them. So, if there is any pass deleting useless insns after you inserted
them, they will get deleted.
Ciao,
Michael.
next parent reply other threads:[~2004-02-23 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040223154755.23916.qmail@web41606.mail.yahoo.com>
2004-02-23 16:42 ` Michael Matz [this message]
2024-03-21 15:12 Centurion
2024-03-21 15:26 ` your mail Segher Boessenkool
2024-03-24 9:30 ` Centurion
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=Pine.LNX.4.58.0402231733260.20969@wotan.suse.de \
--to=matz@suse.de \
--cc=crossgcc@sources.redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gnu.org \
--cc=kripa82@yahoo.com \
/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).