public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yufan8.chen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/60947] [4.9/4.10 Regression] Unable to handle kernel paging request (linux kernel 2.6.28.9) with gcc 4.9 release
Date: Mon, 30 Jun 2014 08:20:00 -0000	[thread overview]
Message-ID: <bug-60947-4-ahd0cB8YzN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60947-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #19 from YuFan <yufan8.chen at gmail dot com> ---

After patching the memset.S, it works correctly.
Thanks a lot.


      parent reply	other threads:[~2014-06-30  8:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24  2:24 [Bug rtl-optimization/60947] New: [4.9 " yufan8.chen at gmail dot com
2014-04-24  2:25 ` [Bug rtl-optimization/60947] " yufan8.chen at gmail dot com
2014-04-24  2:27 ` yufan8.chen at gmail dot com
2014-04-24  2:27 ` yufan8.chen at gmail dot com
2014-04-24  2:28 ` [Bug rtl-optimization/60947] [4.9/4.10 " pinskia at gcc dot gnu.org
2014-04-24  3:43 ` yufan8.chen at gmail dot com
2014-04-24  9:00 ` rguenth at gcc dot gnu.org
2014-04-24 10:01 ` yufan8.chen at gmail dot com
2014-04-24 10:17 ` trippels at gcc dot gnu.org
2014-04-24 10:45 ` yufan8.chen at gmail dot com
2014-04-24 11:22 ` rguenth at gcc dot gnu.org
2014-04-28  9:35 ` yufan8.chen at gmail dot com
2014-05-02  5:31 ` yufan8.chen at gmail dot com
2014-06-25  5:32 ` amker at gcc dot gnu.org
2014-06-25  8:06 ` amker at gcc dot gnu.org
2014-06-25  8:17 ` amker at gcc dot gnu.org
2014-06-26  2:14 ` amker at gcc dot gnu.org
2014-06-26  8:36 ` amker at gcc dot gnu.org
2014-06-26  9:48 ` amker at gcc dot gnu.org
2014-06-30  8:20 ` yufan8.chen at gmail dot com [this message]

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-60947-4-ahd0cB8YzN@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).