public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "revital.eres at linaro dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/47013] FAIL: gcc.dg/sms-*.c scan-rtl-dump-times sms "SMS succeeded" *
Date: Mon, 06 Jun 2011 06:30:00 -0000	[thread overview]
Message-ID: <bug-47013-4-rjoF1Qd1kJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47013-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47013

revital.eres at linaro dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |revital.eres at linaro dot
                   |                            |org

--- Comment #9 from revital.eres at linaro dot org 2011-06-06 06:28:53 UTC ---
(In reply to comment #8)
> Is there any reason (beside reviewing) for not having committed the patch in
> http://gcc.gnu.org/ml/gcc-patches/2011-05/msg01175.html ?

My recent patchs for SMS (i.e.,
http://gcc.gnu.org/ml/gcc-patches/2011-05/msg01341.html), which are not
approved yet, require some adjustments for this testsuite patch. So that's why
I thought it will be better to wait for a approval for the new patches before
pinging for the testsuite patch, avoiding the need to submit a follow-up fix
for it. Also, currently trunk bootstrap is broken on ARM with SMS flags and I'm
trying to figure out the problem... so once I'll locate this problem I'll go
back to these patches and push them forward to trunk.


  parent reply	other threads:[~2011-06-06  6:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-19 14:29 [Bug testsuite/47013] New: " dominiq at lps dot ens.fr
2010-12-20  9:08 ` [Bug testsuite/47013] " eres at il dot ibm.com
2010-12-20  9:26 ` eres at il dot ibm.com
2010-12-20 10:21 ` dominiq at lps dot ens.fr
2010-12-20 10:55 ` eres at il dot ibm.com
2010-12-20 10:59 ` dominiq at lps dot ens.fr
2010-12-27 14:01 ` eres at il dot ibm.com
2010-12-27 14:07 ` eres at il dot ibm.com
2011-06-05 19:05 ` dominiq at lps dot ens.fr
2011-06-06  6:30 ` revital.eres at linaro dot org [this message]
2011-11-22 14:57 ` iains at gcc dot gnu.org
2011-11-23 19:59 ` revital.eres at linaro dot org
2011-12-12  7:53 ` revitale at gcc dot gnu.org
2012-01-12 16:59 ` dominiq at lps dot ens.fr
2012-01-12 17:03 ` dominiq at lps dot ens.fr

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-47013-4-rjoF1Qd1kJ@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).