From: "Alex Hill via gcc-help" <gcc-help@gcc.gnu.org>
To: "Jim Wilson" <jimw@sifive.com>
Cc: "Segher Boessenkool" <segher@kernel.crashing.org>,
gcc-help <gcc-help@gcc.gnu.org>
Subject: Re[8]: GCC won`t emit my instriction
Date: Tue, 18 Jun 2019 04:08:00 -0000 [thread overview]
Message-ID: <1560830894.792978043@f193.i.mail.ru> (raw)
In-Reply-To: <CAFyWVaZL0a9hhKKxPY9S3ifdd+FgwbUeEtt-Mwt-kWTv1-4Zfw@mail.gmail.com>
>Вторник, 18 июня 2019, 3:02 +05:00 от Jim Wilson <jimw@sifive.com>:
>
>On Mon, Jun 17, 2019 at 4:34 AM Alex Hill < hardest2005@mail.ru > wrote:
>> I`m still looking for the way to emit minmax, now i`m try to find solution in
>> ifcvt.c, is there exist a way to dump conditional execution step by step,
>>
>> I read more than thousand pages from documents from gnu.gcc.org, try to find in internet but i can`t find how to dump
>> every step of rtl passes, for example 243.r.ce1, there is only general info in dumps receivced by fdump-rtl-all.
>> In 243.r.ce1 just told "df_analyze called" and nothing else.
>
>You can append a -all to get more info, e.g. -fdump-rtl-ce1-all will
>emit more info than -fdump-rtl-ce1. This will only emit info where
>the optimization pass has hooks to dump debugging info. If you need
>more info than that, you should be stepping through the code in gdb
>We have gdb macros in the .gdbinit file that you can use to pretty
>print rtl, etc. The pr macro will pretty print an rtl pointer.
>
>Jim
i`am using key -da it gives the same result as -all-all or -ce1-all, i`m trying to understand what he is writes to me in dumps, but there is lack of info, except comments in sources, i can`t find any books or electronic resource with infos. Its looks for me as some research in depths of sources of GCC, but i will find the way to emit my instruction no matter what costs!!!!
Sorry for my Engrish
Kind regards Alex Hill.
prev parent reply other threads:[~2019-06-18 4:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 4:42 Alex Hill via gcc-help
2019-06-07 4:50 ` Jeff Law
2019-06-07 5:37 ` Re[2]: " Alex Hill via gcc-help
2019-06-07 16:34 ` Segher Boessenkool
2019-06-10 6:15 ` Re[2]: " Alex Hill via gcc-help
2019-06-10 22:20 ` Jim Wilson
2019-06-11 8:32 ` Re[4]: " Alex Hill via gcc-help
2019-06-11 20:54 ` Jim Wilson
2019-06-17 11:34 ` Re[6]: " Alex Hill via gcc-help
2019-06-17 22:01 ` Jim Wilson
2019-06-18 4:08 ` Alex Hill via gcc-help [this message]
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=1560830894.792978043@f193.i.mail.ru \
--to=gcc-help@gcc.gnu.org \
--cc=hardest2005@mail.ru \
--cc=jimw@sifive.com \
--cc=segher@kernel.crashing.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).