public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libitm/51830] FAIL: libitm.c/mem(cpy|set)-1.c execution test
Date: Wed, 18 Jan 2012 18:52:00 -0000 [thread overview]
Message-ID: <bug-51830-4-eUaNn7wxlF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51830-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51830
Uros Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|unassigned at gcc dot |ubizjak at gmail dot com
|gnu.org |
Target Milestone|--- |4.7.0
--- Comment #2 from Uros Bizjak <ubizjak at gmail dot com> 2012-01-18 18:13:17 UTC ---
I have a patch in testing.
next prev parent reply other threads:[~2012-01-18 18:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 21:44 [Bug other/51830] New: " dominiq at lps dot ens.fr
2012-01-12 8:58 ` [Bug libitm/51830] " rguenth at gcc dot gnu.org
2012-01-18 18:52 ` ubizjak at gmail dot com [this message]
2012-01-18 20:18 ` ubizjak at gmail dot com
2012-01-23 15:12 ` uros at gcc dot gnu.org
2012-01-23 15:13 ` ubizjak at gmail dot com
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-51830-4-eUaNn7wxlF@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).