From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3346 invoked by alias); 28 Dec 2002 23:06:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 3332 invoked by uid 71); 28 Dec 2002 23:06:00 -0000 Date: Sat, 28 Dec 2002 15:06:00 -0000 Message-ID: <20021228230600.3331.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: =?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?= Subject: Re: c++/1920: g++ -O1 optimization bug in casting a reference argument Reply-To: =?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?= X-SW-Source: 2002-12/txt/msg01356.txt.bz2 List-Id: The following reply was made to PR c++/1920; it has been noted by GNATS. From: =?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?= To: mdejong@redhat.com, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c++/1920: g++ -O1 optimization bug in casting a reference argument Date: Sun, 29 Dec 2002 00:02:26 +0100 Notice that the extension from (gcc)Lvalues explicitly rules out taking the address of a cast lvalue. Following the rationale for this restriction, I believe the extension should also not allow passing a cast lvalue as a reference. In addition, -pedantic should produce diagnostics if the extension is used. Regards, Martin