From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Neil Booth <neil@daikokuya.co.uk>,
Diego Novillo <dnovillo@redhat.com>, Phil Edwards <phil@jaj.com>,
Andreas Jaeger <aj@suse.de>,
gcc@gcc.gnu.org
Subject: Re: tree-ssa-cvs corrupt
Date: Mon, 06 Jan 2003 01:06:00 -0000 [thread overview]
Message-ID: <m38yxzm8e3.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <87smw7gpkp.fsf@egil.codesourcery.com>
Zack Weinberg <zack@codesourcery.com> writes:
| Neil Booth <neil@daikokuya.co.uk> writes:
|
| > Zack Weinberg wrote:-
| >> The trouble is that #error causes cpplib's parse_in.errors to be
| >> bumped, but that doesn't propagate back to errorcount until
| >> cpp_finish() is called, from c_common_finish.
| >
| > Merge the diagnostic handlers.
|
| A good idea, but I'm beginning to worry about cpplib ceasing to be
| useful as a standalone library.
Not just because cpplib uses diagnostic.[ch] means it would cease being
a standalone library. Improvement may be applied to both sides.
-- Gaby
next prev parent reply other threads:[~2003-01-06 0:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 16:06 Andreas Jaeger
2003-01-03 16:29 ` Diego Novillo
2003-01-03 16:34 ` Diego Novillo
2003-01-03 16:58 ` Andreas Jaeger
2003-01-03 20:55 ` Mike Stump
2003-01-04 0:35 ` Phil Edwards
2003-01-05 7:46 ` Zack Weinberg
2003-01-05 21:06 ` Diego Novillo
2003-01-05 21:33 ` Neil Booth
2003-01-05 23:07 ` Zack Weinberg
2003-01-05 23:07 ` Neil Booth
2003-01-05 23:18 ` Zack Weinberg
2003-01-05 23:37 ` Neil Booth
2003-01-06 0:27 ` Zack Weinberg
2003-01-06 1:06 ` Gabriel Dos Reis [this message]
2003-01-06 22:57 ` Geoff Keating
2003-01-06 23:20 ` Neil Booth
2003-01-07 1:33 ` Richard Henderson
2003-01-07 1:34 ` Richard Henderson
2003-01-07 2:34 ` Diego Novillo
2003-01-03 16:22 Jason Merrill
2003-01-05 22:14 Bonzini
2003-01-05 22:53 ` Neil Booth
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=m38yxzm8e3.fsf@uniton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=aj@suse.de \
--cc=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=neil@daikokuya.co.uk \
--cc=phil@jaj.com \
--cc=zack@codesourcery.com \
/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).