public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/46893] [4.5/4.6 Regression] ICE: in trunc_int_for_mode, at explow.c:56 with -O -g Date: Thu, 16 Dec 2010 17:11:00 -0000 [thread overview] Message-ID: <bug-46893-4-vPAMLfsRD0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46893-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46893 Alexandre Oliva <aoliva at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aoliva at gcc dot gnu.org |jakub at gcc dot gnu.org --- Comment #6 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2010-12-16 17:10:52 UTC --- Sorry, I was thinking nonsense. Jakub, your patch is good, go for it. The other changes I made, even in as much as they make sense on their own, were a result of the misunderstanding that led me down the wrong path, and to suspect your patch's correctness Now I see they're probably not useful, so I withdraw them.
next prev parent reply other threads:[~2010-12-16 17:11 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-11 4:56 [Bug debug/46893] New: " zsojka at seznam dot cz 2010-12-15 1:24 ` [Bug debug/46893] " hjl.tools at gmail dot com 2010-12-15 10:17 ` jakub at gcc dot gnu.org 2010-12-16 4:43 ` aoliva at gcc dot gnu.org 2010-12-16 4:49 ` aoliva at gcc dot gnu.org 2010-12-16 8:02 ` jakub at gcc dot gnu.org 2010-12-16 14:48 ` rguenth at gcc dot gnu.org 2010-12-16 17:11 ` aoliva at gcc dot gnu.org [this message] 2010-12-16 17:14 ` jakub at gcc dot gnu.org 2010-12-16 19:47 ` [Bug debug/46893] [4.5 " jakub at gcc dot gnu.org 2011-01-16 20:26 ` jakub at gcc dot gnu.org 2011-01-17 8:27 ` jakub at gcc dot gnu.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=bug-46893-4-vPAMLfsRD0@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: 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).