public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "yroux at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/62308] A bug with aarch64 big-endian Date: Wed, 03 Sep 2014 06:08:00 -0000 [thread overview] Message-ID: <bug-62308-4-2GXnFgopx3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62308-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62308 Yvan Roux <yroux at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmakarov at gcc dot gnu.org, | |yroux at gcc dot gnu.org --- Comment #4 from Yvan Roux <yroux at gcc dot gnu.org> --- yes, and there is no issue when we use reload instead of LRA (flag -mno-lra).
next prev parent reply other threads:[~2014-09-03 6:08 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-29 15:16 [Bug rtl-optimization/62308] New: " yml6087582 at 163 dot com 2014-09-01 9:42 ` [Bug target/62308] " rguenth at gcc dot gnu.org 2014-09-02 15:31 ` yml6087582 at 163 dot com 2014-09-02 15:43 ` ktkachov at gcc dot gnu.org 2014-09-03 6:08 ` yroux at gcc dot gnu.org [this message] 2014-10-07 10:38 ` venkataramanan.kumar at amd dot com 2014-10-08 16:38 ` venkataramanan.kumar at amd dot com 2014-10-14 14:22 ` vmakarov at gcc dot gnu.org 2014-10-29 3:09 ` fei.yang0953 at gmail dot com 2015-05-28 12:02 ` clyon at gcc dot gnu.org 2015-05-29 16:02 ` vmakarov at gcc dot gnu.org 2015-06-01 22:06 ` clyon at gcc dot gnu.org 2015-06-18 17:39 ` clyon at gcc dot gnu.org 2015-06-19 14:42 ` clyon at gcc dot gnu.org 2015-06-19 14:58 ` clyon at gcc dot gnu.org 2015-06-19 15:01 ` clyon 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-62308-4-2GXnFgopx3@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: linkBe 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).