public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Sebor <msebor@redhat.com>
To: David Edelsohn <dje.gcc@gmail.com>, Jakub Jelinek <jakub@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Merge from gomp-4_5-branch to trunk
Date: Fri, 06 Nov 2015 17:03:00 -0000	[thread overview]
Message-ID: <563CDD62.7090002@redhat.com> (raw)
In-Reply-To: <CAGWvnyn0nr=3m9c2VvhDkXLKsQYYmSNtMPDpvUW4VXb3N=Yt8g@mail.gmail.com>

On 11/05/2015 09:08 PM, David Edelsohn wrote:
> Sorry for the incorrect blame.  I thought the failure was due to GOMP
> changes, but it appears to be due to the placement new size changes.
> I am re-testing after Martin's fix.
>
> By the way, Martin, the ChangeLog entry is wrong

I've fixed the ChangeLog.

With Jason's help, I've also figured out why I missed the libstdc++
boostrap breakage. I've been assuming that make bootstrap invoked
after a change to the compiler rebuilds libstdc++ and any other
libraries. That apparently isn't the case. I will need to adjust
my workflow to avoid this problem in the future. If there is a page
on the Wiki or somewhere with best practices or recommended steps
that someone knows about, I'd be grateful for a pointer.

Again, sorry for the breakage.

Martin

>
> 2015-11-05  Martin Sebor  <msebor@redhat.com>
>
>          PR c++/67942
>          * invoke.texi (-Wplacement-new): Document new option.
>          * gcc/testsuite/g++.dg/warn/Wplacement-new-size.C: New test.
>
> The invoke.texi change should list doc/invoke.texi and the testsuite
> change should go in testsuite/ChangeLog.
>
> Thanks, David
>

  reply	other threads:[~2015-11-06 17:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06  4:08 David Edelsohn
2015-11-06 17:03 ` Martin Sebor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-11-06  3:37 David Edelsohn
2015-11-05 15:30 Jakub Jelinek
2015-11-05 15:41 ` Nathan Sidwell
2015-11-06 11:15   ` Thomas Schwinge
2015-11-06 16:46     ` Thomas Schwinge
2015-11-08 11:28 ` Thomas Schwinge

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=563CDD62.7090002@redhat.com \
    --to=msebor@redhat.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).