public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eric.weddington at atmel dot com" <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 05:38:00 -0000	[thread overview]
Message-ID: <bug-52488-4-rqRHg4E5u0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52488-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Eric Weddington <eric.weddington at atmel dot com> 2012-03-13 05:37:45 UTC ---
(In reply to comment #7)
> ../../../../../../gcc-4.7.0-RC-20120302/newlib/libc/posix/glob.c:206:1: error:
> allocating 2050 bytes of stack is more than 'at90s2313' can provide
> make[8]: *** [lib_a-glob.o] Error 1
> 
> => Progress, at least no ICE. 
> 
> However, this warning still leaves users in unclearity as GCC doesn't tell the
> maximum of stack it can provide.

You can look up in the device datasheet to see how much RAM it has. 

Or do you want GCC to print out how much RAM each device has?

> 
> > or whatever and
> > tries to build insane code with 2050 bytes of stack for device(s) with only 128
> > bytes of RAM.
> Well, my view is different: The avr's default set of multilib variants is
> non-suitable as general default set of multlib variants. It probably is
> suiteable as set of multilibs for bare-metal targets, but does not meet the
> demands of OSes. 

Do you have recommendations? Or better still, a patch?


  parent reply	other threads:[~2012-03-13  5:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05  7:40 [Bug target/52488] New: " ralf_corsepius at rtems dot org
2012-03-11 22:31 ` [Bug target/52488] " gjl at gcc dot gnu.org
2012-03-12  6:22 ` ralf_corsepius at rtems dot org
2012-03-12 11:12 ` gjl at gcc dot gnu.org
2012-03-12 12:38 ` gjl at gcc dot gnu.org
2012-03-12 12:55 ` jakub at gcc dot gnu.org
2012-03-12 14:16 ` gjl at gcc dot gnu.org
2012-03-13  3:28 ` ralf_corsepius at rtems dot org
2012-03-13  5:38 ` eric.weddington at atmel dot com [this message]
2012-03-13  6:17 ` ralf_corsepius at rtems dot org
2012-03-13  7:03 ` j at uriah dot heep.sax.de
2012-03-13 11:26 ` gjl at gcc dot gnu.org
2012-03-13 11:29 ` gjl at gcc dot gnu.org
2012-03-13 17:04 ` ralf_corsepius at rtems dot org
2012-03-13 18:19 ` gjl at gcc dot gnu.org
2012-03-22 15:13 ` gjl at gcc dot gnu.org
2012-03-22 15:36 ` gjl at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-52488-4-rqRHg4E5u0@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).