public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gang.chen at asianux dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/58400] gcc for h8300 internal compiler error: insn does not satisfy its constraints at  fs/ext4/mballoc.c: In function 'mb_free_blocks':
Date: Thu, 12 Sep 2013 04:00:00 -0000	[thread overview]
Message-ID: <bug-58400-4-Wmn2OI851U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58400-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58400

--- Comment #2 from Chen Gang <gang.chen at asianux dot com> ---
For gcc-4.8.0 and gcc-4.7.4, it has this issue too.


  parent reply	other threads:[~2013-09-12  4:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12  3:58 [Bug c/58400] New: " gang.chen at asianux dot com
2013-09-12  3:59 ` [Bug c/58400] " gang.chen at asianux dot com
2013-09-12  4:00 ` gang.chen at asianux dot com [this message]
2013-09-12  4:02 ` gang.chen at asianux dot com
2013-09-13  3:12 ` gang.chen at asianux dot com
2013-09-13 20:42 ` law at redhat dot com
2013-09-13 20:42 ` law at redhat dot com
2013-09-13 20:43 ` law at redhat dot com
2013-09-13 20:44 ` law at redhat dot com
2014-03-06 12:21 ` [Bug target/58400] " amylaar at gcc dot gnu.org
2015-01-21 10:00 ` gang.chen.5i5j at gmail dot com
2015-02-01  5:16 ` ysato at users dot sourceforge.jp
2015-02-02  1:43 ` gang.chen.5i5j at gmail dot com
2015-02-02 14:10 ` law at redhat dot com
2015-02-02 19:59 ` gang.chen.5i5j at gmail dot com
2015-02-02 20:24 ` joern.rennecke at embecosm dot com
2015-02-03  0:11 ` law at redhat dot com
2015-02-03 12:19 ` gang.chen.5i5j at gmail dot com
2015-02-05 17:05 ` law at redhat dot com
2015-02-05 17:21 ` law at redhat 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-58400-4-Wmn2OI851U@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).