public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schnetter at aei dot mpg dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/19182] New: Error messages seem to be printed slower
Date: Tue, 28 Dec 2004 20:32:00 -0000 [thread overview]
Message-ID: <20041228203205.19182.schnetter@aei.mpg.de> (raw)
When I compare the speed of the screen output of, say, gcc and gfortran, then
it seems to me as if gfortran produced its output much more slowly. gcc's
output seems to appear line by line, whereas gfortran's output seems to appear
character by character. This could be caused by gfortran flushing after every
character instead of after every line or something similar. I'm wondering,
does gfortran do something special when it outputs diagnostic messages? There
has to be some difference -- gfortran's messages do look different, as
gfortran tries to print a cute "pointer" indicating the offending column,
which gcc does not.
--
Summary: Error messages seem to be printed slower
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: schnetter at aei dot mpg dot de
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19182
next reply other threads:[~2004-12-28 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 20:32 schnetter at aei dot mpg dot de [this message]
2004-12-28 20:45 ` [Bug fortran/19182] " pinskia at gcc dot gnu dot org
2004-12-28 20:47 ` pinskia at gcc dot gnu dot org
2004-12-28 21:41 ` tobi at gcc dot gnu dot org
2004-12-28 22:31 ` schnetter at aei dot mpg dot de
2004-12-28 22:34 ` Andrew Pinski
2004-12-28 22:35 ` pinskia at physics dot uc dot edu
2005-01-04 23:55 ` tobi at gcc dot gnu dot org
2005-01-08 0:05 ` tobi at gcc dot gnu dot org
2005-01-16 17:44 ` cvs-commit at gcc dot gnu dot org
2005-01-16 17:51 ` tobi at gcc dot gnu dot org
2005-01-16 17:55 ` 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=20041228203205.19182.schnetter@aei.mpg.de \
--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).