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 middle-end/20506] verify_stmts calls error() on internal errors Date: Thu, 17 Mar 2005 00:24:00 -0000 [thread overview] Message-ID: <20050317002454.22722.qmail@sourceware.org> (raw) In-Reply-To: <20050317001912.20506.reichelt@gcc.gnu.org> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-17 00:24 ------- This is done also at the rtl level and nobody has complained before until now. If we use internal_error, well it just stops at the first error and then we don't know and we try to fix one error and then we get another, which sucks. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20506
next prev parent reply other threads:[~2005-03-17 0:24 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-17 0:19 [Bug middle-end/20506] New: " reichelt at gcc dot gnu dot org 2005-03-17 0:24 ` pinskia at gcc dot gnu dot org [this message] 2005-06-18 1:23 ` [Bug middle-end/20506] verify_stmts calls error() on internal errors(notes) pinskia at gcc dot gnu dot org 2005-06-18 1:24 ` pinskia 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=20050317002454.22722.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).