From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11515 invoked by alias); 1 May 2004 15:03:57 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 11506 invoked by alias); 1 May 2004 15:03:57 -0000 Date: Sat, 01 May 2004 15:03:00 -0000 Message-ID: <20040501150357.11505.qmail@sources.redhat.com> From: "anton at a0 dot complang dot tuwien dot ac dot at" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040501142654.15242.anton@mips.complang.tuwien.ac.at> References: <20040501142654.15242.anton@mips.complang.tuwien.ac.at> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug optimization/15242] pessimization of "goto *" X-Bugzilla-Reason: CC X-SW-Source: 2004-05/txt/msg00055.txt.bz2 List-Id: ------- Additional Comments From anton at a0 dot complang dot tuwien dot ac dot at 2004-05-01 15:03 ------- Subject: Re: pessimization of "goto *" pinskia at gcc dot gnu dot org wrote: > Note jumping out of a statement expression is really illegal and should not be done. Statement expressions are used here just to produce a way to include a statement sequence in a macro. Do you recommend that we should switch from ({ ... }) to do { ... } while (0) ? Or do you have a different suggestion? BTW, looking in the gcc-3.4.0 manual, I don't see the restrictions you mention, and gcc-3.4.0 -Wall also does not complain about this usage. Actually the manual explicitly says: |(If you use some other kind of statement last within the braces, the |construct has type `void', and thus effectively no value.) which I would interpret as "Anything goes, as long as you don't use the value of the statement expression". - anton -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15242