From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8291 invoked by alias); 13 Dec 2010 20:16:38 -0000 Received: (qmail 8281 invoked by uid 22791); 13 Dec 2010 20:16:37 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 13 Dec 2010 20:16:33 +0000 From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/46916] gcc.dg/torture/stackalign/non-local-goto-[1,2].c ICEs compiler due to r167727 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Date: Mon, 13 Dec 2010 20:16:00 -0000 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: 2010-12/txt/msg01491.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D46916 --- Comment #10 from Iain Sandoe 2010-12-13 20:1= 6:23 UTC --- perhaps it would be safer to name the fallback section: >> : darwin_sections[text_unlikely_fallback_section]); >> DEF_SECTION (text_unlikely_fallback_section, SECTION_CODE|SECTION_NO_ANC= HOR, ".section __TEXT,__unlikely_flbk,regular,pure_instructions", 0) (limit of 16chars for the section name =3D=3D "unlikely fallback" ) then there's no danger of a section name clash when someone tries to build= =20 named_section ( "__TEXT,__unlikely,regular,pure_instruction", .... ) (If the regtest works w/out this, then perhaps not necessary ... )