From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4934 invoked by alias); 31 Aug 2006 02:50:23 -0000 Received: (qmail 4896 invoked by uid 48); 31 Aug 2006 02:50:15 -0000 Date: Thu, 31 Aug 2006 02:50:00 -0000 Message-ID: <20060831025015.4895.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/28896] conditional trap goes messed up In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "pinskia at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-08/txt/msg02740.txt.bz2 List-Id: ------- Comment #1 from pinskia at gcc dot gnu dot org 2006-08-31 02:50 ------- Actually it is not just -fstack-limit-symbol that could go wrong but it is also builtin_trap: (define_insn "conditional_trap" [(trap_if (match_operator 0 "valid_dbcc_comparison_p" [(cc0) (const_int 0)]) (match_operand:SI 1 "const_int_operand" "I"))] "TARGET_68020 && ! flags_in_68881 ()" Are you sure you supplied the correct flags to the compiler because conditional_trap is only enabled for 020. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|m68k port quietly accepts - |conditional trap goes messed |fstack-limit-symbol on |up |ColdFire | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28896