This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

[PATCH] Move error_operand_p one level up

From: Paolo Carlini <paolo dot carlini at oracle dot com>
To: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
Cc: Ian Lance Taylor <iant at google dot com>, Jason Merrill <jason at redhat dot com>
Date: Fri, 10 Jun 2011 11:58:33 +0200
Subject: [PATCH] Move error_operand_p one level up

Hi,

yesterday I noticed that, as I vaguely suspected for quite some time, error_operand_p can be useful also outside the c++ front-end. The below, which I bootstrapped c, c++, go, on x86_64-linux (and I'm finishing testing) tries to do that, moving the macro one level up and using it in all the suitable places I spotted.

What do people think?

Thanks,
Paolo.

////////////////////

Attachment: CL_error_operand_p
Description: Text document

Attachment: patch_error_operand_p
Description: Text document

Follow-Ups:
- Re: [PATCH] Move error_operand_p one level up
  - From: Richard Guenther

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]