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]

Re: [PATCH c/c++/ada/middle-end 1/2]: Merging meaning of CONVERT_EXPR and NOP_EXPR v.3

From: Paolo Bonzini <bonzini at gnu dot org>
To: Tomas Bily <tomby at atrey dot karlin dot mff dot cuni dot cz>
Cc: gcc-patches at gcc dot gnu dot org, tbily at suse dot cz
Date: Thu, 21 Aug 2008 16:02:02 +0200
Subject: Re: [PATCH c/c++/ada/middle-end 1/2]: Merging meaning of CONVERT_EXPR and NOP_EXPR v.3
References: <20080821134527.GA12057@atrey.karlin.mff.cuni.cz>

In contruction

  if (something)
	(void)0;
  else
	.....

(void) 0 is represented as CONVERT_EXPR (void, int (0)). After merging
CONVERT_EXPR/NOP_EXPR meaning CONVERT_EXPR (void, int (0)) will have
same meaning as NOP_EXPR (void, int(0)) that represent empty stmt. It
has same meaning as

 if (something)
	;

Excuse me the stupid question, but the two do look the same to me. Why should they be treated differently?

Paolo

Follow-Ups:
- Re: [PATCH c/c++/ada/middle-end 1/2]: Merging meaning of CONVERT_EXPR and NOP_EXPR v.3
  - From: Tomas Bily

References:
- [PATCH c/c++/ada/middle-end 1/2]: Merging meaning of CONVERT_EXPR and NOP_EXPR v.3
  - From: Tomas Bily

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