public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kazu at cs dot umass dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/13874] ICE on valid code - tif-lzw.i Date: Tue, 27 Jan 2004 04:10:00 -0000 [thread overview] Message-ID: <20040127041002.25280.qmail@sources.redhat.com> (raw) In-Reply-To: <20040127023022.13874.tm@kloo.net> ------- Additional Comments From kazu at cs dot umass dot edu 2004-01-27 04:09 ------- I think I've fixed that on mainline. Yes, I was running your stress test on m32r and found that. http://gcc.gnu.org/ml/gcc-patches/2004-01/msg00014.html Maybe just matter of waiting for next merge. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |kazu at cs dot umass dot edu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13874
next prev parent reply other threads:[~2004-01-27 4:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-27 2:30 [Bug optimization/13874] New: " tm at kloo dot net 2004-01-27 2:32 ` [Bug optimization/13874] " tm at kloo dot net 2004-01-27 4:10 ` kazu at cs dot umass dot edu [this message] 2004-01-27 5:08 ` [Bug target/13874] [tree-ssa] [merge] " pinskia at gcc dot gnu dot org 2004-01-30 18:37 ` pinskia 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=20040127041002.25280.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).