From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1268 invoked by alias); 12 Jul 2005 18:47:37 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 1255 invoked by uid 22791); 12 Jul 2005 18:47:34 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 12 Jul 2005 18:47:34 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j6CIkRX8019524; Tue, 12 Jul 2005 14:46:27 -0400 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j6CIkQV26958; Tue, 12 Jul 2005 14:46:26 -0400 Received: from topo.toronto.redhat.com (vpn50-40.rdu.redhat.com [172.16.50.40]) by pobox.toronto.redhat.com (8.12.8/8.12.8) with ESMTP id j6CIkP1M024722; Tue, 12 Jul 2005 14:46:25 -0400 Received: from topo.toronto.redhat.com (localhost.localdomain [127.0.0.1]) by topo.toronto.redhat.com (8.13.4/8.13.4) with ESMTP id j6CIkIjr006359; Tue, 12 Jul 2005 14:46:19 -0400 Received: (from dnovillo@localhost) by topo.toronto.redhat.com (8.13.4/8.13.4/Submit) id j6CIkI2H006358; Tue, 12 Jul 2005 14:46:18 -0400 Date: Tue, 12 Jul 2005 18:47:00 -0000 From: Diego Novillo To: Ian Lance Taylor Cc: "Joseph S. Myers" , gcc@gcc.gnu.org Subject: Re: Some tests in gcc.c-torture rely on undefined behaviour? Message-ID: <20050712184618.GA6309@topo.toronto.redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-SW-Source: 2005-07/txt/msg00516.txt.bz2 On Tue, Jul 12, 2005 at 11:39:18AM -0700, Ian Lance Taylor wrote: > I would guess that 920612-1.c, at least, could just be changed to use > unsigned int, and it would continue to test whatever bug it was > testing when it was originally added. > The problem is somewhat more widespread now with the tree optimizers. In particular with old test cases. Some of these cases are essentially optimized into empty functions by the time we get into the RTL passes. We would have to audit them all and add enough external functions, volatile markers or what-have-you to have them survive until RTL. Not sure if it's worth it.