From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27493 invoked by alias); 1 Sep 2010 06:33:41 -0000 Received: (qmail 27474 invoked by uid 48); 1 Sep 2010 06:33:40 -0000 Date: Wed, 01 Sep 2010 06:33:00 -0000 From: "hp at sourceware dot org" To: gdb-prs@sourceware.org Message-ID: <20100901063340.11965.hp@sourceware.org> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug sim/11965] New: vmhaddshs, vmhraddshs uninitialized variable may cause wrong VSCR result X-Bugzilla-Reason: CC Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2010-q3/txt/msg00348.txt.bz2 Looking at sim/ppc/altivec.igen 1.4 it seems the sat variable for vmhaddshs and vmhraddshs isn't initialized before being "|=" in the vector element loop, so depending on what the host and compiler makes of it, VSCR (from calling ALTIVEC_SET_SAT) may be set incorrectly. I guess not many codes looks at it, hence going undetected until now. Just a random observation, no test-case or anything. Not even sure I see right. :) -- Summary: vmhaddshs, vmhraddshs uninitialized variable may cause wrong VSCR result Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: sim AssignedTo: unassigned at sourceware dot org ReportedBy: hp at sourceware dot org CC: gdb-prs at sourceware dot org GCC target triplet: powerpc-* http://sourceware.org/bugzilla/show_bug.cgi?id=11965 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.