From: <sje@cup.hp.com>
To: abel@ispras.ru
Cc: gcc-patches@gcc.gnu.org, wilson@tuliptree.org, vmakarov@redhat.com
Subject: Re: Selective scheduling pass - target changes (ia64 & rs6000) [3/3]
Date: Thu, 25 Sep 2008 22:39:00 -0000 [thread overview]
Message-ID: <1222379001.869560.14444.nullmailer@hpsje.cup.hp.com> (raw)
In-Reply-To: <48AEDCA5.1080909@ispras.ru>
Andrey,
I have started looking at the IA64 specific parts of the selective
scheduling branch. I still need some more time but I was wondering if you
could update it so that it is up-to-date with respect to the main trunk.
I tried to apply the patch so I could look at some of the changes with
more context and ia64.c would not apply cleanly.
Here are a few minor comments from what I have reviewed so far. I didn't
include the patch and put the comments inline since the patch is so
large and I only had a few comments.
There are some places where lines start with spaces instead of tabs even
though they are indented enough to use tabs and a couple of functions
(ia64_sched_init and ia64_sched_final) had lines where the only change
was from tabs to spaces.
In ia64_clear_sched_context we free _sc->prev_cycle_state, I was
wondering if we should set it to NULL after freeing it. Or are
we going to free _sc right after this so that it doesn't matter?
Is the mflag_sched_spec_verbose flag really needed? It looks like
all it does is dump output to stderr intead of the normal dump file.
In get_mode_no_for_insn, there is a check:
(AR_CCV_REGNUM <= REGNO (reg) && REGNO (reg) <= AR_EC_REGNUM)
I think this should be replaced with AR_REGNO_P ().
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2008-09-25 21:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 14:24 [RFC] Selective scheduling pass Andrey Belevantsev
2008-06-03 14:26 ` Selective scheduling pass - middle end changes [1/1] Andrey Belevantsev
2008-06-11 1:04 ` Ian Lance Taylor
2008-06-11 13:40 ` Andrey Belevantsev
2008-06-11 14:30 ` Ian Lance Taylor
2008-06-27 13:10 ` Andrey Belevantsev
2008-06-30 16:16 ` Ian Lance Taylor
2008-07-08 14:54 ` Andrey Belevantsev
2008-07-08 15:29 ` Ian Lance Taylor
2008-08-22 15:55 ` Andrey Belevantsev
2008-06-03 14:27 ` Selective scheduling pass - scheduler changes [2/3] Andrey Belevantsev
2008-06-03 22:03 ` Vladimir Makarov
2008-08-22 15:52 ` Andrey Belevantsev
2008-06-03 14:28 ` Selective scheduling pass - target changes (ia64 & rs6000) [3/3] Andrey Belevantsev
2008-08-22 16:04 ` Andrey Belevantsev
2008-08-29 13:41 ` [Ping] [GWP/ia64/rs6000 maintainer needed] " Andrey Belevantsev
2008-08-29 15:01 ` Mark Mitchell
2008-09-25 22:39 ` sje [this message]
2008-09-26 14:57 ` Andrey Belevantsev
2008-10-03 22:22 ` Steve Ellcey
2008-10-06 17:26 ` Andrey Belevantsev
2008-06-03 22:03 ` [RFC] Selective scheduling pass Vladimir Makarov
2008-06-04 16:55 ` Mark Mitchell
2008-06-04 20:50 ` Andrey Belevantsev
2008-06-05 3:45 ` Seongbae Park (박성배, 朴成培)
2008-06-05 13:49 ` Andrey Belevantsev
2008-08-29 15:10 Selective scheduling pass - target changes (ia64 & rs6000) [3/3] David Edelsohn
2008-08-31 13:35 ` Andrey Belevantsev
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=1222379001.869560.14444.nullmailer@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=abel@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=vmakarov@redhat.com \
--cc=wilson@tuliptree.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).