From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8807 invoked by alias); 16 Sep 2002 07:26: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 8788 invoked by uid 71); 16 Sep 2002 07:26:00 -0000 Resent-Date: 16 Sep 2002 07:26:00 -0000 Resent-Message-ID: <20020916072600.8787.qmail@sources.redhat.com> Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer) Resent-Cc: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org Resent-Reply-To: gcc-gnats@gcc.gnu.org, mschill4@ix.urz.uni-heidelberg.de Received: (qmail 8575 invoked by uid 61); 16 Sep 2002 07:24:22 -0000 Message-Id: <20020916072422.8574.qmail@sources.redhat.com> Date: Mon, 16 Sep 2002 00:26:00 -0000 From: mschill4@ix.urz.uni-heidelberg.de Reply-To: mschill4@ix.urz.uni-heidelberg.de To: gcc-gnats@gcc.gnu.org X-Send-Pr-Version: gnatsweb-2.9.3 (1.1.1.1.2.31) Subject: libstdc++/7926: i486 instructions in header files make c++ programs crash on i386 X-SW-Source: 2002-09/txt/msg00447.txt.bz2 List-Id: >Number: 7926 >Category: libstdc++ >Synopsis: i486 instructions in header files make c++ programs crash on i386 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Sep 16 00:26:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Manuel Tobias Schiller >Release: gcc-3.2 >Organization: >Environment: i388 running Linux 2.2.21 and glibc 2.2.5 >Description: When configuring and building gcc 3.2 on a i386-linux machine c++ programs fail because you use 486 code in inline assembler statements in your atomicity headers (xadd, cmpxchg and others) libjava has the same problems. It would be nice if you could rework the header files to use non-atomic i386 instructions if such behaviour is required. A special configure option would do, too. If you need help how the appropriate headers for i386 might look like, mail me, but I haven't got the files around here at the university, so it might take some time to send them in... >How-To-Repeat: You can't repeat it unless you still have an old i386 around... >Fix: rework i386 atomicity header files to make a distinction between i386 and i486 and newer... >Release-Note: >Audit-Trail: >Unformatted: