From: Joseph Myers <joseph@codesourcery.com>
To: Paul Koning <paulkoning@comcast.net>
Cc: Tom de Vries <tdevries@suse.de>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
<gcc@gcc.gnu.org>, Richard Biener <rguenther@suse.de>,
Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: [RFC] Update Stage 4 description
Date: Wed, 09 Jan 2019 16:33:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1901091632140.22775@digraph.polyomino.org.uk> (raw)
In-Reply-To: <846F367A-8DFA-43DC-B0C5-EBFFB068628C@comcast.net>
On Wed, 9 Jan 2019, Paul Koning wrote:
> Is there, or should there be, a distinction between primary and
> non-primary platforms? While platform bugs typically require fixes in
> platform-specific code, I would think we would want to stay away from
> bugfixes in minor platforms during stage 4. The wording seems to say
> that I could fix wrong-code bugs in pdp11 during stage 4; I have been
> assuming I should not do that. Is this something that should be
> explicitly stated?
In target-specific code for a minor target you can more or less do as you
want - but the decision on when to branch won't take account of what
you're doing for a minor target, so any major work runs the risk of the
branch happening at an unstable point in the middle of that work.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2019-01-09 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 8:41 Tom de Vries
2019-01-09 8:47 ` Richard Biener
2019-01-09 9:20 ` [wwwdocs, committed] " Tom de Vries
2019-01-09 9:02 ` [RFC] " Jonathan Wakely
2019-01-09 15:14 ` Nathan Sidwell
2019-01-09 14:16 ` Paul Koning
2019-01-09 14:31 ` Richard Biener
2019-01-09 16:33 ` Joseph Myers [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=alpine.DEB.2.21.1901091632140.22775@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=paulkoning@comcast.net \
--cc=rguenther@suse.de \
--cc=tdevries@suse.de \
/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).