public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8889: g++ 3.2.1 (also 3.2 it) miscompile Qt Date: Mon, 16 Dec 2002 17:26:00 -0000 [thread overview] Message-ID: <20021217012601.16049.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8889; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: Felix von Leitner <felix-gcc@fefe.de> Cc: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/8889: g++ 3.2.1 (also 3.2 it) miscompile Qt Date: Mon, 16 Dec 2002 17:25:09 -0800 Felix von Leitner <felix-gcc@fefe.de> writes: > I made a bug report and you refuse to even make a feeble attempt to > reproduce it. Instead you first claim that it's an ABI problem (which > is not and I wrote that), then you claim you need more information (you > don't, I included everything that is necessary to reproduce the problem) > and then you claim that I withhold necessary information. As a matter of project policy, the GCC team expects you to do more of the work of isolating the bug. I would like to draw your attention to http://gcc.gnu.org/bugs.html, which clearly states that you are expected to provide a self-contained, already preprocessed, as small as feasible, source file which is being miscompiled, along with an explanation of what it is supposed to do and what it does instead. We make this requirement because our experience is that, in a circumstance such as yours, we would be unable to reproduce the bug by downloading the software packages you mentioned and compiling them ourselves. Tiny differences in system headers, for instance, can perturb the bug out of manifesting. We would then have wasted a great deal of effort. zw
next reply other threads:[~2002-12-17 1:26 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-16 17:26 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-16 17:06 Felix von Leitner 2002-12-16 16:08 bangerth 2002-12-16 16:06 Wolfgang Bangerth 2002-12-16 16:06 Wolfgang Bangerth 2002-12-16 15:26 Wolfgang Bangerth 2002-12-16 13:06 Wolfgang Bangerth 2002-12-16 12:56 Felix von Leitner 2002-12-16 11:26 bangerth 2002-12-12 8:12 reichelt 2002-12-12 7:06 Felix von Leitner 2002-12-12 2:50 reichelt
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=20021217012601.16049.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).