From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-385899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 32670 invoked by alias); 13 Mar 2012 07:03:59 -0000
Received: (qmail 32661 invoked by uid 22791); 13 Mar 2012 07:03:58 -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; Tue, 13 Mar 2012 07:03:45 +0000
From: "j at uriah dot heep.sax.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52488] avr-*:  internal compiler error: in extract_insn, at recog.c:2123
Date: Tue, 13 Mar 2012 07:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: j at uriah dot heep.sax.de
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.7.1
X-Bugzilla-Changed-Fields: CC
Message-ID: <bug-52488-4-FWCyX70xwG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52488-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52488-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2012-03/txt/msg00952.txt.bz2

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52488

Joerg Wunsch <j at uriah dot heep.sax.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |j at uriah dot heep.sax.de

--- Comment #10 from Joerg Wunsch <j at uriah dot heep.sax.de> 2012-03-13 07:02:51 UTC ---
(In reply to comment #9)

> > Or do you want GCC to print out how much RAM each device has?
> No, I would expect GCC to print its rationale for this rejection.
> 
> e.g. something like 
> "allocating 2050 byte of stack exceeds maximum stack size (1024 bytes) ..."

There is no fixed stack size in GCC.  It's just the SRAM size sets an
upper limit for the largest possible stack size.  Thus Eric's question
about printing out the RAM size.