public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/64581] [5 Regression] libffi/testsuite/libffi.special/special.exp doesn't use newly built GCC
Date: Wed, 14 Jan 2015 23:51:00 -0000	[thread overview]
Message-ID: <bug-64581-4-b0L0LYVOpw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64581-4@http.gcc.gnu.org/bugzilla/>

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-01-14
                 CC|                            |rth at gcc dot gnu.org
   Target Milestone|---                         |5.0
            Summary|libffi/testsuite/libffi.spe |[5 Regression]
                   |cial/special.exp doesn't    |libffi/testsuite/libffi.spe
                   |use newly built GCC         |cial/special.exp doesn't
                   |                            |use newly built GCC
     Ever confirmed|0                           |1

--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
r219477 wiped out all GCC customization.  We need to investigate them
and put them back if needed.


  reply	other threads:[~2015-01-14 23:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 11:54 [Bug libffi/64581] New: " hjl.tools at gmail dot com
2015-01-14 23:51 ` hjl.tools at gmail dot com [this message]
2015-01-15 21:51 ` [Bug libffi/64581] [5 Regression] " rth at gcc dot gnu.org
2015-01-20 21:26 ` rth at gcc dot gnu.org
2015-01-20 21:30 ` rth 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-64581-4-b0L0LYVOpw@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).