public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/44181] -fcompare-debug failure (length) with -Os -fgraphite-identity Date: Fri, 11 Jun 2010 12:24:00 -0000 [thread overview] Message-ID: <20100611122353.22488.qmail@sourceware.org> (raw) In-Reply-To: <bug-44181-14164@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from aoliva at gcc dot gnu dot org 2010-06-11 12:23 ------- Created an attachment (id=20887) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20887&action=view) Patch that fixes the problem Here's the patch I'm testing now. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44181
next prev parent reply other threads:[~2010-06-11 12:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-17 23:43 [Bug tree-optimization/44181] New: " zsojka at seznam dot cz 2010-05-17 23:45 ` [Bug tree-optimization/44181] " zsojka at seznam dot cz 2010-06-11 12:23 ` aoliva at gcc dot gnu dot org 2010-06-11 12:24 ` aoliva at gcc dot gnu dot org [this message] 2010-06-11 12:29 ` aoliva at gcc dot gnu dot org 2010-06-11 12:57 ` [Bug debug/44181] " aoliva at gcc dot gnu dot org 2010-06-14 19:19 ` aoliva at gcc dot gnu dot org 2010-06-14 19:22 ` aoliva 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=20100611122353.22488.qmail@sourceware.org \ --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).