From: Marek Polacek <polacek@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR56344
Date: Mon, 02 Dec 2013 19:19:00 -0000 [thread overview]
Message-ID: <20131202191916.GH9986@redhat.com> (raw)
In-Reply-To: <20131202164033.GF9986@redhat.com>
On Mon, Dec 02, 2013 at 05:40:33PM +0100, Marek Polacek wrote:
> On Mon, Dec 02, 2013 at 04:01:05PM +0100, Richard Biener wrote:
> > On Wed, Mar 13, 2013 at 1:57 PM, Marek Polacek <polacek@redhat.com> wrote:
> > > Ping.
> >
> > Ok. (yay, oldest patch in my review queue ...)
>
> ;) thanks. Just to be sure, did you mean to ok this patch (that is,
> the one with HOST_BITS_PER_INT)?
>
> Bootstrap/regtest in progress.
>
> 2013-12-02 Marek Polacek <polacek@redhat.com>
>
> PR middle-end/56344
> * calls.c (expand_call): Disallow passing huge arguments
> by value.
>
> --- gcc/calls.c.mp4 2013-12-02 17:12:18.621057873 +0100
> +++ gcc/calls.c 2013-12-02 17:32:35.523684716 +0100
> @@ -3047,6 +3047,15 @@ expand_call (tree exp, rtx target, int i
> {
> rtx before_arg = get_last_insn ();
>
> + /* We don't allow passing huge (> 2^30 B) arguments
> + by value. It would cause an overflow later on. */
> + if (adjusted_args_size.constant
> + >= (1 << (HOST_BITS_PER_INT - 1)))
Surely I meant to use "HOST_BITS_PER_INT - 2" here.
Marek
next prev parent reply other threads:[~2013-12-02 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 18:27 Marek Polacek
2013-02-26 23:17 ` Joseph S. Myers
2013-02-27 9:56 ` Marek Polacek
2013-02-27 11:33 ` Richard Biener
2013-02-27 17:38 ` Joseph S. Myers
2013-03-01 8:41 ` Richard Biener
2013-03-05 16:06 ` Marek Polacek
2013-03-13 12:57 ` Marek Polacek
2013-12-02 15:01 ` Richard Biener
2013-12-02 16:40 ` Marek Polacek
2013-12-02 19:19 ` Marek Polacek [this message]
2013-12-02 20:35 ` Richard Biener
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=20131202191916.GH9986@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=richard.guenther@gmail.com \
/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).