public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61331] [ARM] GCC build broken since r210964/r210965
Date: Thu, 29 May 2014 08:14:00 -0000	[thread overview]
Message-ID: <bug-61331-4-cNS1ErYZyf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61331-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
(In reply to rsandifo@gcc.gnu.org from comment #5)
> (In reply to Bernd Edlinger from comment #4)
> > (In reply to rsandifo@gcc.gnu.org from comment #3)
> > > (In reply to Bernd Edlinger from comment #2)
> > > > Richard,
> > > > 
> > > > the build is still broken, even after r211031.
> > > > 
> > > > could you please have a look?
> > > 
> > > r211031 wasn't related to this.  Please see:
> > > 
> > > https://gcc.gnu.org/ml/gcc-patches/2014-05/msg02312.html
> > > 
> > > for the patch I'd suggested.
> > 
> > Ok, this would fix the boot-strap problem.
> > Are you gonna apply it now?
> 
> It needs to be approved by a maintainer first.

well, did not explicitly ask for approval?

The message should be marked as PATCH,
and contain a statement like:

"Boot-strapped and regression-tested on arm-xyz-eabi,
OK for thunk"?


  parent reply	other threads:[~2014-05-29  8:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 14:58 [Bug target/61331] New: [ARM] GCC build broken since r210964/r210954 christophe.lyon at st dot com
2014-05-27 14:58 ` [Bug target/61331] " christophe.lyon at st dot com
2014-05-28 22:56 ` [Bug target/61331] [ARM] GCC build broken since r210964/r210965 bernd.edlinger at hotmail dot de
2014-05-29  6:47 ` rsandifo at gcc dot gnu.org
2014-05-29  7:38 ` bernd.edlinger at hotmail dot de
2014-05-29  8:00 ` rsandifo at gcc dot gnu.org
2014-05-29  8:14 ` bernd.edlinger at hotmail dot de [this message]
2014-05-31 13:49 ` bernd.edlinger at hotmail dot de
2014-06-02 11:33 ` rsandifo at gcc dot gnu.org
2014-07-10  9:07 ` ktkachov 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-61331-4-cNS1ErYZyf@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).