public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dann at godzilla dot ics dot uci dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/15690] compilation stops after the first file with errors
Date: Fri, 28 May 2004 13:27:00 -0000 [thread overview]
Message-ID: <20040527202446.12601.qmail@sourceware.org> (raw)
In-Reply-To: <20040527181206.15690.dann@godzilla.ics.uci.edu>
------- Additional Comments From dann at godzilla dot ics dot uci dot edu 2004-05-27 20:24 -------
(In reply to comment #3)
> Also most of the time you are not
> passing more than one file to the driver.
In that case the old and new behavior are completely identical.
In the case you are passing multiple files (and a lot of people do) then you'd
want to see all the errors from all files for the same reasons you want to see
all the errors within a file.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15690
next prev parent reply other threads:[~2004-05-27 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 7:40 [Bug driver/15690] New: " dann at godzilla dot ics dot uci dot edu
2004-05-28 8:05 ` [Bug driver/15690] " pinskia at gcc dot gnu dot org
2004-05-28 11:27 ` dann at godzilla dot ics dot uci dot edu
2004-05-28 11:28 ` pinskia at gcc dot gnu dot org
2004-05-28 13:27 ` dann at godzilla dot ics dot uci dot edu [this message]
2004-06-25 23:31 ` [Bug driver/15690] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-11-30 2:06 ` [Bug driver/15690] [4.0 " pinskia at gcc dot gnu dot org
2004-11-30 2:07 ` pinskia at gcc dot gnu dot org
2004-11-30 22:12 ` dpatel at apple dot com
2004-12-01 16:21 ` pinskia at gcc dot gnu dot org
2004-12-11 7:45 ` 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=20040527202446.12601.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).