public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "falk at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/39002] codegen bug?
Date: Wed, 28 Jan 2009 14:44:00 -0000 [thread overview]
Message-ID: <20090128144400.27270.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39002-11564@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from falk at debian dot org 2009-01-28 14:44 -------
(In reply to comment #4)
> What I can try is finding the revision which causes the fault.
While that would certainly be helpful, it's unlikely that anybody would be
willing to debug this without a usable testcase.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39002
next prev parent reply other threads:[~2009-01-28 14:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 14:18 [Bug c++/39002] New: " r dot emrich at de dot tecosim dot com
2009-01-28 14:21 ` [Bug c++/39002] " r dot emrich at de dot tecosim dot com
2009-01-28 14:22 ` r dot emrich at de dot tecosim dot com
2009-01-28 14:25 ` falk at debian dot org
2009-01-28 14:27 ` r dot emrich at de dot tecosim dot com
2009-01-28 14:44 ` falk at debian dot org [this message]
2009-01-28 14:45 ` r dot emrich at de dot tecosim dot com
2009-01-28 14:57 ` r dot emrich at de dot tecosim dot com
2009-01-28 16:52 ` r dot emrich at de dot tecosim dot com
2009-01-28 17:01 ` r dot emrich at de dot tecosim dot com
2009-01-28 17:02 ` r dot emrich at de dot tecosim dot com
2009-01-28 17:06 ` r dot emrich at de dot tecosim dot com
2009-01-28 18:04 ` r dot emrich at de dot tecosim dot com
2009-01-28 19:06 ` r dot emrich at de dot tecosim dot com
2009-01-29 8:05 ` [Bug target/39002] codegen bug, stack pointer is not restored ubizjak at gmail dot com
2009-01-29 8:06 ` [Bug target/39002] [4,4 Regression] " ubizjak at gmail dot com
2009-01-29 10:31 ` [Bug target/39002] [4.4 " jakub at gcc dot gnu dot org
2009-01-29 10:47 ` r dot emrich at de dot tecosim dot com
2009-01-29 11:35 ` r dot emrich at de dot tecosim dot com
2009-01-29 12:04 ` jakub at gcc dot gnu dot org
2009-01-29 12:21 ` ktietz at gcc dot gnu dot org
2009-01-29 12:27 ` ktietz at gcc dot gnu dot org
2009-01-29 12:53 ` ktietz at gcc dot gnu dot org
2009-01-29 13:24 ` jakub at gcc dot gnu dot org
2009-01-29 13:46 ` ktietz at gcc dot gnu dot org
2009-01-29 13:54 ` jakub at gcc dot gnu dot org
2009-01-29 14:05 ` ktietz at gcc dot gnu dot org
2009-01-29 14:34 ` jakub at gcc dot gnu dot org
2009-01-29 22:48 ` sezeroz at gmail dot com
2009-01-30 8:54 ` ktietz at gcc dot gnu dot org
2009-01-30 9:23 ` jakub at gcc dot gnu dot org
2009-01-30 9:29 ` jakub 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=20090128144400.27270.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: 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).