From: Neil Booth <neil@daikokuya.co.uk>
To: Zack Weinberg <zack@codesourcery.com>
Cc: 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: Sun, 05 Jan 2003 23:07:00 -0000 [thread overview]
Message-ID: <20030105230701.GA19498@daikokuya.co.uk> (raw)
In-Reply-To: <8765t342qy.fsf@egil.codesourcery.com>
Zack Weinberg wrote:-
> Neil Booth <neil@daikokuya.co.uk> writes:
>
> >> > A distant voice on the wind whispers "#error ..."
> >> >
> >> The wind replies "we still try to compile the file anyway ..."
> >
> > Yeah, #error should stop compilation like the standard requires. I've
> > never gotten round to fixing it. CPP would need a way to stop it lexing
> > any more tokens (not too hard), and a way to signal to the front end to
> > not do any more work.
>
> 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.
>
> We can't just change that line you quoted to
>
> if (errorcount || sorrycount || cpp_errors (&parse_in))
>
> because that will screw over non-C front ends. Ideas?
Merge the diagnostic handlers.
Neil.
next prev parent reply other threads:[~2003-01-05 23:07 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 [this message]
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
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=20030105230701.GA19498@daikokuya.co.uk \
--to=neil@daikokuya.co.uk \
--cc=aj@suse.de \
--cc=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--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).