public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Marek Polacek <polacek@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR56344
Date: Tue, 26 Feb 2013 23:17:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1302262315110.339@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20130226182733.GG25197@redhat.com>

On Tue, 26 Feb 2013, Marek Polacek wrote:

> +	      /* 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 << 30))
> +	        {
> +	          error ("passing too large argument on stack");
> +		  continue;

This should be sorry () not error (), as a compiler limitation rather than 
a defect in the user's program.  (And is input_location set to something 
useful here so the diagnostic points to the argument in question rather 
than e.g. to the end of the function containing the problem call?)

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2013-02-26 23:17 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 [this message]
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
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=Pine.LNX.4.64.1302262315110.339@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=polacek@redhat.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).