From: David Kastrup <dak@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Dmitry Antipov <dmantipov@yandex.ru>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Enlarge MAX_ALLOCA?
Date: Fri, 20 Jun 2014 11:38:57 +0200 [thread overview]
Message-ID: <877g4b7wem.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <877g4cnd7x.fsf@igel.home> (Andreas Schwab's message of "Fri, 20 Jun 2014 11:26:42 +0200")
Andreas Schwab <schwab@linux-m68k.org> writes:
> Dmitry Antipov <dmantipov@yandex.ru> writes:
>
>> IIUC this means that if alloca is limited to < 32K, stack may be expanded
>> with just one instruction because increment fits into an immediate operand.
>> Otherwise there should be a few more load/store/add instructions.
>
> If you use alloca you have a variable sized stack frame, so the offset
> will be variable as well.
Ah right, alloca is generally not something affecting the code
generation of unrelated code, so arrays allocated with alloca do not
change the offsets of scalar stack variables which are usually addressed
off a separate frame pointer unaffected by alloca.
So the addressing mode restrictions I brought up would be a red herring,
even when talking about something like 68k architectures. So it seems
like indeed just the total stack size available (or not available) in
connection with the expected stack depth particularly including
functions using alloca that should govern the chosen sizes.
--
David Kastrup
next prev parent reply other threads:[~2014-06-20 9:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 16:02 Enlarge MAX_ALLOCA? Eli Zaretskii
2014-06-19 16:23 ` David Kastrup
2014-06-19 16:48 ` Eli Zaretskii
2014-06-19 17:04 ` David Kastrup
2014-06-19 17:14 ` Eli Zaretskii
2014-06-19 17:36 ` David Kastrup
2014-06-19 17:51 ` Eli Zaretskii
2014-06-19 18:21 ` Stefan Monnier
2014-06-19 21:13 ` David Kastrup
2014-06-20 7:10 ` Eli Zaretskii
2014-06-20 8:08 ` David Kastrup
2014-06-20 8:38 ` Dmitry Antipov
2014-06-20 8:56 ` Eli Zaretskii
2014-06-20 9:26 ` Andreas Schwab
2014-06-20 9:38 ` David Kastrup [this message]
2014-06-19 18:28 ` Stefan Monnier
2014-06-19 18:38 ` Eli Zaretskii
2014-06-19 20:37 ` Stefan Monnier
2014-06-20 7:08 ` Eli Zaretskii
2014-06-20 13:02 ` Stefan Monnier
2014-06-20 13:18 ` Eli Zaretskii
2014-06-20 14:43 ` Stefan Monnier
2014-06-20 14:50 ` Eli Zaretskii
2014-06-20 15:15 ` Herring, Davis
2014-06-20 15:44 ` Dmitry Antipov
2014-06-20 18:36 ` Eli Zaretskii
2014-06-21 13:01 ` K. Handa
2014-06-21 13:59 ` Eli Zaretskii
2014-06-21 17:08 ` Stefan Monnier
2014-06-22 9:22 ` K. Handa
2014-06-28 14:15 ` K. Handa
2014-06-28 14:38 ` Eli Zaretskii
2014-06-21 15:19 ` David Kastrup
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877g4b7wem.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=dmantipov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).