From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27230 invoked by alias); 28 Jan 2009 13:52:46 -0000 Received: (qmail 27183 invoked by uid 48); 28 Jan 2009 13:52:32 -0000 Date: Wed, 28 Jan 2009 13:52:00 -0000 Message-ID: <20090128135232.27182.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug testsuite/36443] [4.3/4.4 Regression]: HOSTCC doesn't work with installed gcc In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "rob1weld at aol dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-01/txt/msg03088.txt.bz2 ------- Comment #40 from rob1weld at aol dot com 2009-01-28 13:52 ------- Notes from 38820: I had "Known to fail" set to 4.4.0 4.3.2 Another 'proof' this is a Bug. You are allowed to build GCC after you set (reasonable) Environment variables. Examples are: export set CC="gcc -v" export set CC="gcc -mregparm=2" export set CC="gcc -msseregparm" export set CC="gcc gcc -ffloat-store -msse4 -mfpmath=sse,387" Further support for the argument that this is a Bug is shown in "info gcc" : `-mregparm=NUM' `-msseregparm' *Warning:* if you use this switch, and NUM is nonzero, then you must build all modules with the same value, including any libraries. This includes the system libraries and startup modules. You are allowed to compile GCC in this manner (and may desire to do so for testing purposes). If you do build GCC this way then GCC_EXEC_PREFIX must be set correctly (to the newly compiled system libraries and startup modules). Rob -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36443