From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15870 invoked by alias); 15 Mar 2003 17:46:04 -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 15748 invoked by uid 71); 15 Mar 2003 17:46:04 -0000 Date: Sat, 15 Mar 2003 17:46:00 -0000 Message-ID: <20030315174604.15738.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Andreas Schwab Subject: Re: middle-end/10011: [ppc] Broken __builtin_constant_p Reply-To: Andreas Schwab X-SW-Source: 2003-03/txt/msg01013.txt.bz2 List-Id: The following reply was made to PR middle-end/10011; it has been noted by GNATS. From: Andreas Schwab To: bangerth@dealii.org Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: middle-end/10011: [ppc] Broken __builtin_constant_p Date: Sat, 15 Mar 2003 18:41:32 +0100 bangerth@dealii.org writes: |> Old Synopsis: Broken __builtin_constant_p |> New Synopsis: [ppc] Broken __builtin_constant_p It's not ppc specific, ia64 has the same problem. |> Thanks, Andreas, for double-checking. Is this a regression |> against previous versions? We should mark it as this then! Yes, it's a regression against 3.3. Andreas. -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."