From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27595 invoked by alias); 10 Mar 2010 16:36:21 -0000 Received: (qmail 27569 invoked by uid 22791); 10 Mar 2010 16:36:20 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail2.rz.htw-berlin.de (HELO mail2.rz.htw-berlin.de) (141.45.10.102) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 10 Mar 2010 16:36:15 +0000 Envelope-to: gcc-help@gcc.gnu.org Received: from e178117215.adsl.alicedsl.de ([85.178.117.215] helo=[192.168.178.6]) by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1NpOtJ-0000dQ-5T for gcc-help@gcc.gnu.org; Wed, 10 Mar 2010 17:36:13 +0100 Message-ID: <4B97CA7C.2020607@htw-berlin.de> Date: Wed, 10 Mar 2010 16:36:00 -0000 From: Thomas Martitz Reply-To: thomas.martitz@student.htw-berlin.de User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100307 Lightning/1.0b1 Icedove/3.0.3 MIME-Version: 1.0 To: gcc-help@gcc.gnu.org Subject: Re: Problems migrating to gcc 4.4.3&eabi - apparently a gcc bug References: <4B9677C1.6040502@htw-berlin.de> <4B967A4D.8060905@redhat.com> <4B968150.8010004@htw-berlin.de> <4B96953E.10305@redhat.com> <4B96994D.40904@htw-berlin.de> <4B96A58B.6010503@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de) X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2010-03/txt/msg00150.txt.bz2 Am 10.03.2010 16:55, schrieb Ian Lance Taylor: > Andrew Haley writes: > > >> Yeah, it's a bug. Mind you, it's pretty bizarre code: I'm not surprised >> we never came across this before. >> > Bizarre or not, please report it following the guidelines at > http://gcc.gnu.org/bugs/ . Thanks. > > Ian > I will gather the required information and post the bug reported. Thanks for the help so far! Best regards.