public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Nicholas Clifton <nickc@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: RFA: Fix calculation of size of builtin setjmp buffer
Date: Tue, 06 May 2014 14:40:00 -0000	[thread overview]
Message-ID: <20140506144026.GX1817@tucnak.redhat.com> (raw)
In-Reply-To: <5368F2FD.9080604@redhat.com>

On Tue, May 06, 2014 at 03:34:37PM +0100, Nicholas Clifton wrote:
> --- gcc/except.c	(revision 210096)
> +++ gcc/except.c	(working copy)
> @@ -286,8 +286,8 @@
>        tmp = size_int (FIRST_PSEUDO_REGISTER + 2 - 1);
>  #endif
>  #else
> -      /* builtin_setjmp takes a pointer to 5 words.  */
> -      tmp = size_int (5 * BITS_PER_WORD / POINTER_SIZE - 1);
> +      /* builtin_setjmp uses a buffer big enough to hold 5 pointers.  */
> +      tmp = size_int (5 * POINTER_SIZE / BITS_PER_WORD - 1);

But what will this do on targets where POINTER_SIZE is smaller than
BITS_PER_WORD?  E.g. I think some options on s390 or ppc.
If you want it to be always 5 pointers, then you want
  tmp = size_int (4);
and not something else, otherwise it really depends on how exactly it is
used, perhaps it can be 5 * MAX (BITS_PER_WORD / POINTER_SIZE, 1) - 1
or whatever else, but 5 * POINTER_SIZE / BITS_PER_WORD is definitely wrong.

>  #endif
>        tmp = build_index_type (tmp);
>        tmp = build_array_type (ptr_type_node, tmp);

	Jakub

  parent reply	other threads:[~2014-05-06 14:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 12:55 Nick Clifton
2014-05-06 13:15 ` Jakub Jelinek
2014-05-06 14:34   ` Nicholas Clifton
2014-05-06 14:38     ` Richard Biener
2014-05-06 14:40     ` Jakub Jelinek [this message]
2014-05-06 15:07       ` Nicholas Clifton
2014-05-06 20:17         ` Mike Stump
2014-05-08 14:25           ` Nicholas Clifton
2014-05-08 16:08             ` Mike Stump
2014-05-14  8:23               ` Eric Botcazou
2014-05-14  8:17 ` Eric Botcazou
2014-05-14 13:32   ` Nicholas Clifton
2014-05-15  7:56     ` Eric Botcazou
2014-05-15 14:49       ` Mike Stump
2014-05-16 16:56         ` Eric Botcazou
2014-05-16  8:29       ` Nicholas Clifton
2014-05-16 16:57         ` Eric Botcazou

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=20140506144026.GX1817@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nickc@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).