From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12312 invoked by alias); 10 Dec 2004 10:11:42 -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 12280 invoked by uid 48); 10 Dec 2004 10:11:37 -0000 Date: Fri, 10 Dec 2004 10:11:00 -0000 Message-ID: <20041210101137.12279.qmail@sourceware.org> From: "ebotcazou at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041124222749.18665.skunk@iskunk.org> References: <20041124222749.18665.skunk@iskunk.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug target/18665] [3.4/4.0 Regression] -ftrapv borks up simple integer arithmetic X-Bugzilla-Reason: CC X-SW-Source: 2004-12/txt/msg01451.txt.bz2 List-Id: ------- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-12-10 10:11 ------- OK, I understand what happens: the 5 symbols __absvdi2, __addvdi3, __subvdi3, __mulvdi3 and __negvdi2 are not #defined in libgcc2.h, hence not tweaked based on the word size. They are, therefore, double-word symbols everywhere, which doesn't work on 64-bit targets. The fix is straightforward, however there is a hitch: on 64-bit targets, libgcc will contain 5 new symbols (__absvti2, __addvti3, __mulvti3, __negvti2, __subvti3) and will not contain (__absvsi2, __addvsi3, __mulvsi3, __negvsi2, __subvsi3) anymore. While the former is OK, the latter is probably not so we might need to provide stubs that will redirect them to the equivalent mode-sized routines for backwards compatibility. Richard, does that sound plausible? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18665