public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/95353] [10/11 Regression] GCC can't build binutils
Date: Thu, 28 May 2020 15:21:34 +0000	[thread overview]
Message-ID: <bug-95353-4-NC0nnTLqhL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95353-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95353

--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
I test my warning changes with binutils and --enable-targets=all.  But that
apparently doesn't compile all source files, and I don't have a cross-build
setup in place (or the resources to do it).  If someone who already does
cross-builds could periodically post results to gcc-testresults (or report
bugs), or if we could get these going in Jeff's buildbot, that would help catch
the problems in those before either package is released.

  parent reply	other threads:[~2020-05-28 15:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27  2:03 [Bug middle-end/95353] New: " hjl.tools at gmail dot com
2020-05-27  2:05 ` [Bug middle-end/95353] " hjl.tools at gmail dot com
2020-05-27  2:21 ` pinskia at gcc dot gnu.org
2020-05-27  3:15 ` hjl.tools at gmail dot com
2020-05-27  4:58 ` hjl.tools at gmail dot com
2020-05-27  6:42 ` glisse at gcc dot gnu.org
2020-05-27  8:07 ` [Bug tree-optimization/95353] " rguenth at gcc dot gnu.org
2020-05-27 15:15 ` msebor at gcc dot gnu.org
2020-05-28  4:41 ` amodra at gmail dot com
2020-05-28 15:21 ` msebor at gcc dot gnu.org [this message]
2020-05-28 20:10 ` [Bug tree-optimization/95353] [10/11 Regression] spurious -Wstringop-overflow writing to a trailing array plus offset msebor at gcc dot gnu.org
2020-06-03  0:13 ` msebor at gcc dot gnu.org
2020-06-03 16:10 ` msebor at gcc dot gnu.org
2020-06-04 16:18 ` msebor at gcc dot gnu.org
2020-06-10 18:02 ` cvs-commit at gcc dot gnu.org
2020-06-10 18:03 ` [Bug tree-optimization/95353] [10 " msebor at gcc dot gnu.org
2020-06-13 17:32 ` cvs-commit at gcc dot gnu.org
2020-07-23  6:51 ` rguenth at gcc dot gnu.org
2020-08-03 14:41 ` msebor at gcc dot gnu.org
2021-01-06 16:37 ` msebor at gcc dot gnu.org
2021-01-21 22:51 ` msebor at gcc dot gnu.org

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=bug-95353-4-NC0nnTLqhL@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).