public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8442: Wrongful compiler error - file available Date: Mon, 04 Nov 2002 08:56:00 -0000 [thread overview] Message-ID: <20021104165604.612.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8442; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: Juan Carlos Arevalo-Baeza <jcab@JCABs-Rumblings.com> Cc: gcc-bugs@gcc.gnu.org, <gcc-prs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: c++/8442: Wrongful compiler error - file available Date: Mon, 4 Nov 2002 10:58:35 -0600 (CST) > Yes, Spirit is a complex beast. I'm sorry about that. I've tried > extracting the error bits, but I've been uncuccessful so far. It seems Start from the .ii file you have. First delete all the # lines, I use the following perl script for that usually perl -pi -s 's/^#.*\n//g;' your_file.ii (This way, gcc tells you the real location in the file where something is happening, not the location in the file from which you generated the .ii file.) Then start deleting parts of the file that are not necessary to show the problem. (Function bodies, classes that are only referenced in the function bodies you deleted, classes and namespaces that were only used in classes and namespaces you deleted, etc). In the beginning, the pieces you scrap are usually small, but the blocks can become very large at the end, so don't be scared if you don't make much progress in the beginning. This is a tedious task, and may take an hour or two, but in the end you usually end up with something that has 10-50 lines of code and still shows the problem. With such an example, it is also possible for someone who is not used to your code to see whether this is wrong or right. Otherwise, it is very hard to see... Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-11-04 16:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-04 8:56 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-05 6:46 Reichelt 2002-11-05 0:36 Juan Carlos Arevalo-Baeza 2002-11-04 8:56 Juan Carlos Arevalo-Baeza 2002-11-04 7:55 bangerth 2002-11-03 17:56 jcab
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=20021104165604.612.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --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).