public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/13906] genmodes.c:964: internal compiler error: Bus error in md5_process_block Date: Thu, 29 Jan 2004 01:03:00 -0000 [thread overview] Message-ID: <20040129010342.22153.qmail@sources.redhat.com> (raw) In-Reply-To: <20040128234527.13906.danglin@gcc.gnu.org> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-01-29 01:03 ------- It does not happen without --enable-checking because md5 is not used. The problem is that md5_process_block believes it is okay to have unaligned words. This will effect 3.5.0 also if PCH and includes are used and the buffer is not word aligned. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|bootstrap |other Ever Confirmed| |1 Keywords| |build Last reconfirmed|0000-00-00 00:00:00 |2004-01-29 01:03:40 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13906
next prev parent reply other threads:[~2004-01-29 1:03 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-28 23:45 [Bug bootstrap/13906] New: " danglin at gcc dot gnu dot org 2004-01-29 1:03 ` pinskia at gcc dot gnu dot org [this message] 2005-07-03 15:38 ` [Bug other/13906] " cvs-commit at gcc dot gnu dot org 2005-07-03 15:40 ` cvs-commit at gcc dot gnu dot org 2005-07-07 7:26 ` brian at dessent dot net 2005-07-07 14:56 ` dj at redhat dot com 2005-07-08 0:59 ` brian at dessent dot net 2005-07-12 21:25 ` sje at cup dot hp dot com [not found] <bug-13906-276@http.gcc.gnu.org/bugzilla/> 2006-02-06 13:49 ` ghazi at gcc dot gnu dot org 2006-02-06 14:07 ` ghazi at gcc dot gnu dot org 2006-02-06 14:07 ` ghazi at gcc dot gnu dot 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=20040129010342.22153.qmail@sources.redhat.com \ --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).