public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Oleg Endo <oleg.endo@t-online.de>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdocs] SH 4.8 changes update
Date: Sun, 19 Aug 2012 23:38:00 -0000	[thread overview]
Message-ID: <1345419449.2268.38.camel@yam-132-YW-E178-FTW> (raw)
In-Reply-To: <alpine.LNX.2.00.1208192140520.2774@ghan.fvgr>

On Sun, 2012-08-19 at 21:43 +0200, Gerald Pfeifer wrote:
> On Sun, 19 Aug 2012, Oleg Endo wrote:
> > Thanks.  Let's hope that I can squeeze in some more stuff while
> > stage 1 lasts. :T
> 
> You know that for backend-specific changes (especially for "smaller"
> ports) you actually have some more leeway?

You mean, since SH is neither a primary nor a secondary platform, there
are no particular release criteria for it?  What does that actually
mean?

> > But now that you mention it, maybe it would be better to rename the
> > '-menable-tas' option to '-mtas', since other instruction related
> > options do not have 'enabled' in the name.
> 
> Now still would be time to do so without worrying about compatibility. ;-)

True.

Cheers,
Oleg

  reply	other threads:[~2012-08-19 23:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-19  0:47 Oleg Endo
2012-08-19  1:36 ` Kaz Kojima
2012-08-19 17:20 ` Gerald Pfeifer
2012-08-19 18:09   ` Oleg Endo
2012-08-19 19:43     ` Gerald Pfeifer
2012-08-19 23:38       ` Oleg Endo [this message]
2012-08-20 12:24         ` Gerald Pfeifer
2012-08-20 12:31         ` Richard Guenther
2012-08-29 19:25 Oleg Endo
2012-09-02 15:57 ` Gerald Pfeifer
2012-10-04 21:52 Oleg Endo
2012-10-05 12:54 ` Kaz Kojima
2012-10-06 15:57 ` Gerald Pfeifer
2012-10-06 16:48   ` Oleg Endo
2012-10-05 19:36 Oleg Endo

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=1345419449.2268.38.camel@yam-132-YW-E178-FTW \
    --to=oleg.endo@t-online.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.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).