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 other/17900] [4.0 Regression] GCC's source path in ICE is wrong
Date: Fri, 08 Oct 2004 21:43:00 -0000 [thread overview]
Message-ID: <20041008214345.2638.qmail@sourceware.org> (raw)
In-Reply-To: <20041008213920.17900.pinskia@gcc.gnu.org>
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-10-08 21:43 -------
Looks like it was caused by:
* diagnostic.c (text_specifies_location): Delete.
(bug_report_request): Delete.
(diagnostic_set_info): Don't call text_specifies_location.
(diagnostic_action_after_output): Put text from
bug_report_request inline here. Use gcc_unreachable.
(diagnostic_report_current_function): Fix comment.
(diagnostic_report_diagnostic): Clarify logic for error recursion.
Call pp_prepare_to_format before diagnostic_starter.
(trim_filename): Use IS_DIR_SEPARATOR.
(fatal_error, internal_error): Use gcc_unreachable.
(error_recursion): Call diagnostic_action_after_output to
issue the bug_report_request message and exit.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |zack at gcc dot gnu dot org
Target Milestone|--- |4.0.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17900
next prev parent reply other threads:[~2004-10-08 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 21:39 [Bug other/17900] New: " pinskia at gcc dot gnu dot org
2004-10-08 21:43 ` pinskia at gcc dot gnu dot org [this message]
2004-10-09 18:34 ` [Bug other/17900] " pinskia at gcc dot gnu dot org
2004-10-14 3:42 ` bje at gcc dot gnu dot org
2004-10-14 7:04 ` bje at gcc dot gnu dot org
2004-10-14 7:16 ` cvs-commit at gcc dot gnu dot org
2004-10-14 12:22 ` 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=20041008214345.2638.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).