From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11514 invoked by alias); 2 Jul 2005 10:04:54 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 11388 invoked by uid 22791); 2 Jul 2005 10:04:41 -0000 Received: from dublin.act-europe.fr (HELO dublin.act-europe.fr) (212.157.227.154) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 02 Jul 2005 10:04:41 +0000 Received: from localhost (province.act-europe.fr [10.10.0.214]) by filtered-dublin.act-europe.fr (Postfix) with ESMTP id 31BA8229F3B; Sat, 2 Jul 2005 12:04:23 +0200 (MET DST) Received: from dublin.act-europe.fr ([10.10.0.154]) by localhost (province.act-europe.fr [10.10.0.214]) (amavisd-new, port 10024) with ESMTP id 00708-10; Sat, 2 Jul 2005 12:04:23 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by dublin.act-europe.fr (Postfix) with ESMTP id B3F1C229F3A; Sat, 2 Jul 2005 12:04:22 +0200 (MET DST) From: Eric Botcazou To: James E Wilson Subject: Re: MEMBER_TYPE_FORCES_BLK on IA-64/HP-UX Date: Sat, 02 Jul 2005 10:04:00 -0000 User-Agent: KMail/1.7.1 Cc: gcc@gcc.gnu.org References: <200506081226.50599.ebotcazou@adacore.com> <42C5C77D.1050604@specifixinc.com> In-Reply-To: <42C5C77D.1050604@specifixinc.com> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200507021204.45679.ebotcazou@adacore.com> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-SW-Source: 2005-07/txt/msg00061.txt.bz2 > Steve Ellcey defined MEMBER_TYPE_FORCES_BLK when he first implemented > the ia64-hpux port. At the time, I mentioned using PARALLELs was a > better solution, but this was a simpler way for him to get the initial > port working. Since then, there have been a lot of bug fixes to the > ia64-hpux support by various people: Steve, Zack, Joseph, etc. Looking > at the current code, it does appear that all cases are now handled by > PARALLELs, and that the definition of MEMBER_TYPE_FORCES_BLK no longer > appears to be necessary. Running the 2 GCC compatibility testsuites between the unpatched and the patched compiled indeed shows that this part of MEMBER_TYPE_FORCES_BLK is now useless for the purpose it was initially defined. Moreover, removing it doesn't trigger any new failure in the testsuite except in one corner case (a GNU extension); but that can be easily patched in ia64_function_arg. I plan on submitting a patch to Steve and you next week. Thanks for your feedback. -- Eric Botcazou