public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/63285] [4.9 Regression] -fcompare-debug scheduler related failure
Date: Wed, 01 Oct 2014 01:57:00 -0000 [thread overview]
Message-ID: <bug-63285-4-h9ANVssv5X@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63285-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63285
--- Comment #6 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #5)
> Vlad, do you plan to apply this to 4.9 and 4.8 branches too?
> For 4.9, I've bootstrapped/regtested it on
> {x86_64,i686,armv7hl,aarch64}-linux.
Yes, I have plans to commit it for the branches this week. Simply, I wanted to
wait a bit in case if somebody finds issues with the patch.
Jakub, I can do it tomorrow if you want and there are deadlines with releases.
Please, just let me know if there are any deadlines.
next prev parent reply other threads:[~2014-10-01 1:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-63285-4@http.gcc.gnu.org/bugzilla/>
2014-09-17 10:46 ` [Bug debug/63285] [4.9/5 " jakub at gcc dot gnu.org
2014-09-18 16:56 ` vmakarov at gcc dot gnu.org
2014-09-18 19:14 ` vmakarov at gcc dot gnu.org
2014-09-22 10:19 ` [Bug debug/63285] [4.9 " rguenth at gcc dot gnu.org
2014-09-29 15:33 ` jakub at gcc dot gnu.org
2014-10-01 1:57 ` vmakarov at gcc dot gnu.org [this message]
2014-10-01 5:18 ` jakub at gcc dot gnu.org
2014-10-01 14:43 ` jakub at gcc dot gnu.org
2014-10-14 13:51 ` jakub 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-63285-4-h9ANVssv5X@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).