From: Jan Hubicka <hubicka@ucw.cz>
To: gcc-patches@gcc.gnu.org
Subject: Fix alloca handling of very large datastructures
Date: Sun, 30 Nov 2003 23:17:00 -0000 [thread overview]
Message-ID: <20031130210201.GA13522@kam.mff.cuni.cz> (raw)
Hi,
another bug...
Bootstrapped/regtested x86_64-linux, will commit it as obvious.
2003-11-30 Jan Hubicka <jh@suse.cz>
* explow.c (round_push): Fix handling of large sizes.
Index: explow.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/explow.c,v
retrieving revision 1.104.2.1
diff -c -3 -p -r1.104.2.1 explow.c
*** explow.c 11 Apr 2003 22:56:05 -0000 1.104.2.1
--- explow.c 29 Nov 2003 21:34:16 -0000
*************** round_push (size)
*** 947,953 ****
return size;
if (GET_CODE (size) == CONST_INT)
{
! int new = (INTVAL (size) + align - 1) / align * align;
if (INTVAL (size) != new)
size = GEN_INT (new);
}
--- 947,953 ----
return size;
if (GET_CODE (size) == CONST_INT)
{
! HOST_WIDE_INT new = (INTVAL (size) + align - 1) / align * align;
if (INTVAL (size) != new)
size = GEN_INT (new);
}
reply other threads:[~2003-11-30 21:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031130210201.GA13522@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@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).