public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/49191] gcc.dg/memcpy-3.c FAILs on SPARC
Date: Tue, 07 Jun 2011 13:15:00 -0000 [thread overview]
Message-ID: <bug-49191-4-jDUbXOpLiN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49191-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49191
--- Comment #5 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> 2011-06-07 13:13:59 UTC ---
(In reply to comment #4)
> And arm-linux-gnueabi.
Though on ARM I would expect this to pass once we can support unaligned
memcpy's for certain versions of the architecture.
Ramana
next prev parent reply other threads:[~2011-06-07 13:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 13:50 [Bug middle-end/49191] New: " ro at gcc dot gnu.org
2011-05-27 13:56 ` [Bug middle-end/49191] " richard.guenther at gmail dot com
2011-05-27 14:10 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-05-28 14:59 ` danglin at gcc dot gnu.org
2011-06-07 13:12 ` ramana at gcc dot gnu.org
2011-06-07 13:15 ` ramana at gcc dot gnu.org [this message]
2011-06-08 17:38 ` sje at cup dot hp.com
2011-06-08 17:51 ` jakub at gcc dot gnu.org
2011-06-08 17:52 ` jakub at gcc dot gnu.org
2011-06-08 18:00 ` dave at hiauly1 dot hia.nrc.ca
2011-06-08 18:13 ` sje at cup dot hp.com
2011-06-08 19:14 ` ebotcazou at gcc dot gnu.org
2011-06-08 20:07 ` sje at cup dot hp.com
2011-06-26 8:00 ` jakub at gcc dot gnu.org
2011-06-27 17:58 ` jakub at gcc dot gnu.org
2011-06-27 18:10 ` ebotcazou at gcc dot gnu.org
2014-08-20 15:58 ` sje 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-49191-4-jDUbXOpLiN@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).