public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Douglas Mencken <dougmencken@gmail.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	Iain Sandoe <iain@codesourcery.com>
Subject: Re: Please accept this commit for the trunk
Date: Fri, 09 Feb 2018 02:06:00 -0000	[thread overview]
Message-ID: <84113033-9E00-497D-95FE-9BE2742FC899@comcast.net> (raw)
In-Reply-To: <20180208203643.GL21977@gate.crashing.org>

On Feb 8, 2018, at 12:36 PM, Segher Boessenkool <segher@kernel.crashing.org> wrote:
> 
> On Wed, Feb 07, 2018 at 03:52:27PM -0800, Mike Stump wrote:
>> I dusted the pointed to patch off and check it in.  Let us know how it goes.
> 
> I wanted to test this on the primary and secondary powerpc targets as
> well, but okay.

I reviewed it, and it seemed to only trigger for darwin.  Certainly doesn't hurt to run a regression run and ensure that is the case.

>> Does this resolve all of PR84113?  If so, I can push the bug along.
> 
> It makes bootstrap work.  We don't know if it is correct otherwise.

So, would be nice if someone could run a regression test.  I'd do it by the version just before the breakage, and then drop in the patch, and test again.  This minimizes all the other changes.

>> What PR was the attachment url from?
> 
> It is not from a PR, and it has never been sent to gcc-patches; it is
> from https://gcc.gnu.org/ml/gcc-testresults/2017-01/msg02971.html
> (attachment #2).

Ah, that explains it.

Sounds like 1, 3 and 4 also likely need to go it to make things nice.  If someone could regression test and let us know, that's likely the gating factor.

  reply	other threads:[~2018-02-09  2:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 16:42 Douglas Mencken
2018-02-07 23:52 ` Mike Stump
     [not found]   ` <CACYvZ7jH6LG6o7VXfhFrEw=B2kCzfU8qj=Ry9Fat5FGPK-rmJQ@mail.gmail.com>
2018-02-08 17:40     ` Fwd: " Douglas Mencken
2018-02-08 20:36   ` Segher Boessenkool
2018-02-09  2:06     ` Mike Stump [this message]
2018-02-09 17:14       ` Segher Boessenkool

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=84113033-9E00-497D-95FE-9BE2742FC899@comcast.net \
    --to=mikestump@comcast.net \
    --cc=dougmencken@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iain@codesourcery.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).