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 c++/19300] [4.0 Regression] PCH failures on sparc-linux Date: Sun, 16 Jan 2005 01:54:00 -0000 [thread overview] Message-ID: <20050116015411.31794.qmail@sourceware.org> (raw) In-Reply-To: <20050106195542.19300.christian.joensson@gmail.com> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-16 01:54 ------- I cannot decide if I should put this in C++ or debug component based on: http://gcc.gnu.org/ml/gcc-patches/2005-01/msg00871.html But if it was broken by the patch referenced in that email then the testresults does not make sense back from April since that patch only went in September. -- What |Removed |Added ---------------------------------------------------------------------------- Component|other |c++ Keywords| |wrong-debug http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19300
next prev parent reply other threads:[~2005-01-16 1:54 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-06 19:55 [Bug c++/19300] New: PCH failuers " christian dot joensson at gmail dot com 2005-01-06 19:56 ` [Bug other/19300] " pinskia at gcc dot gnu dot org 2005-01-06 20:17 ` [Bug other/19300] PCH failures " ebotcazou at gcc dot gnu dot org 2005-01-06 20:20 ` ebotcazou at gcc dot gnu dot org 2005-01-07 11:03 ` christian dot joensson at gmail dot com 2005-01-07 11:13 ` [Bug other/19300] [4.0 Regression] PCH failures ebotcazou at gcc dot gnu dot org 2005-01-07 13:52 ` [Bug other/19300] [4.0 Regression] PCH failures on sparc-linux pinskia at gcc dot gnu dot org 2005-01-07 18:05 ` christian dot joensson at gmail dot com 2005-01-07 19:21 ` christian dot joensson at gmail dot com 2005-01-07 19:23 ` christian dot joensson at gmail dot com 2005-01-07 20:40 ` pinskia at gcc dot gnu dot org 2005-01-07 20:51 ` pinskia at gcc dot gnu dot org 2005-01-07 20:53 ` pinskia at gcc dot gnu dot org 2005-01-07 20:55 ` pinskia at gcc dot gnu dot org 2005-01-10 7:32 ` christian dot joensson at gmail dot com 2005-01-15 10:50 ` ebotcazou at gcc dot gnu dot org 2005-01-16 1:54 ` pinskia at gcc dot gnu dot org [this message] 2005-01-16 9:10 ` [Bug target/19300] " ebotcazou at gcc dot gnu dot org 2005-01-16 9:15 ` ebotcazou at gcc dot gnu dot org 2005-01-29 14:01 ` pinskia at gcc dot gnu dot org 2005-02-11 17:25 ` phython at gcc dot gnu dot org 2005-02-13 2:24 ` christian dot joensson at gmail dot com 2005-02-14 20:14 ` christian dot joensson at gmail dot com 2005-02-15 23:48 ` cvs-commit at gcc dot gnu dot org 2005-02-16 0:04 ` phython at gcc dot gnu dot org 2005-02-16 0:28 ` pinskia at gcc dot gnu dot org 2005-08-02 19:04 ` cvs-commit at gcc dot gnu dot org 2005-08-02 23:40 ` pinskia at gcc dot gnu dot org 2005-08-04 9:47 ` christian dot joensson at gmail dot com 2005-08-04 10:01 ` ebotcazou 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=20050116015411.31794.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).