From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Housekeeping work in backends.html
Date: Tue, 20 Jan 2015 13:25:00 -0000 [thread overview]
Message-ID: <CABu31nP-z7fEqFDL0=MtHZ=1otSh=j23rxLrctBTCS6Cbh5kGQ@mail.gmail.com> (raw)
In-Reply-To: <3099427.HZad4n1Lxd@polaris>
On Wed, Jan 7, 2015 at 9:42 AM, Eric Botcazou wrote:
>> the attached patch removes obsolete ports (c4x, m68hc11 and ms1), toggles
>> the 'p' letter and adjust accordingly (only avr, fr30, m68k, mcore, rs6000
>> and sh still use define_peephole) and removes trailing spaces.
>
> Same treatment for the 'd' letter, the ports that do not use DFA scheduler
> descriptions are a clear minority (avr, cr16, cris, fr30, h8300, m32c, mmix,
> msp430, pdp11, stormy16, vax). Applied.
Perhaps 'd' should just go away completely. It was intended to
distinguish between ports using the old scheduler description and
ports using the DFA model. But support for the old scheduler
description was removed some 10 years ago, and AFAIR the targets that
don't use the DFA scheduler don't use the scheduler at all.
Ciao!
Steven
next prev parent reply other threads:[~2015-01-20 13:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 23:20 Eric Botcazou
2015-01-06 18:43 ` Jeff Law
2015-01-06 23:04 ` Eric Botcazou
2015-01-06 20:50 ` Sandra Loosemore
2015-01-06 23:16 ` Eric Botcazou
2015-01-06 23:41 ` Eric Botcazou
2015-01-07 0:10 ` Max Filippov
2015-01-07 8:11 ` Eric Botcazou
2015-01-10 0:46 ` Bernd Schmidt
2015-01-13 23:25 ` Eric Botcazou
2015-01-20 9:27 ` Eric Botcazou
2015-01-07 8:44 ` Eric Botcazou
2015-01-20 13:25 ` Steven Bosscher [this message]
2015-01-20 18:45 ` Eric Botcazou
2015-01-21 9:27 ` Eric Botcazou
2015-01-07 9:28 ` Eric Botcazou
2015-01-14 3:55 ` Anthony Green
2015-01-14 9:46 ` Eric Botcazou
2015-01-20 10:59 ` Eric Botcazou
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='CABu31nP-z7fEqFDL0=MtHZ=1otSh=j23rxLrctBTCS6Cbh5kGQ@mail.gmail.com' \
--to=stevenb.gcc@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@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).