public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@adacore.com>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Cc: gcc-patches@gcc.gnu.org,
	Ramana Radhakrishnan <ramana.radhakrishnan@foss.arm.com>
Subject: Re: [ARM] Fix PR middle-end/65958
Date: Tue, 03 Nov 2015 18:05:00 -0000	[thread overview]
Message-ID: <2805623.kLq2Weys6P@polaris> (raw)
In-Reply-To: <5638F077.5050105@foss.arm.com>

> Unless there really is common code between the two patches, this should
> be separated out into two posts, one for ARM and one for AArch64.

The ARM bits were approved by Ramana and installed right away.

> Hmm, so if PROBE_INTERVAL != 4096 we barf!

Yes, but that's not usual, ARM and SPARC have it too, 4096 happens to be the 
limit of reg+off addressing mode on several architectures.

> While that's safe and probably right for Linux, on some OSes there might
> be a minimum page size of 16k or even 64k.  It would be nice if we could
> support that.

OK, but we cannot test anything at the moment.

> Ug!  Manifest constants should be moved to pre-defines.
> PROBE_STACK_BASE_REG?

OK.

> > +
> > +  /* The following code uses indexed address calculation on FIRST.  */
> > +  gcc_assert ((first % 4096) == 0);
> 
> where's 4096 come from?

It's the same constraint as above:

#if (PROBE_INTERVAL % 4096) != 0
#error Cannot use indexed address calculation for stack probing
#endif

to be able to use the 12-bit shifted immediate instructions. 

> More manifest constants.

Yeah, consistency first. ;-)

> This should be annotated with the sequence length.

OK, thanks for the review, I'll adjust.

-- 
Eric Botcazou

  reply	other threads:[~2015-11-03 18:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 16:15 Eric Botcazou
2015-06-17 10:41 ` Ramana Radhakrishnan
2015-06-18 19:03   ` Eric Botcazou
2015-07-06 15:46     ` Ramana Radhakrishnan
2015-09-20 21:05       ` Christophe Lyon
2015-09-21  8:18         ` Eric Botcazou
2015-10-06 10:11       ` Eric Botcazou
2015-10-06 13:43         ` Ramana Radhakrishnan
2015-10-28 11:38           ` Eric Botcazou
2015-10-07  8:15         ` Yao Qi
2015-10-07  9:10           ` Eric Botcazou
2015-10-07 10:42             ` Yao Qi
2015-10-07 17:38               ` Eric Botcazou
2015-11-03 17:35         ` Richard Earnshaw
2015-11-03 18:05           ` Eric Botcazou [this message]
2015-11-03 21:51             ` Eric Botcazou
2015-11-16 20:01           ` Eric Botcazou
2015-11-25  7:56             ` Eric Botcazou
2015-12-03 11:08             ` Richard Earnshaw
2015-12-03 12:20               ` Eric Botcazou
2015-12-04  9:39                 ` Marcus Shawcroft
2015-12-04 11:58                   ` Eric Botcazou
2015-12-04 13:49                 ` Richard Earnshaw
2015-12-04 18:26                   ` 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=2805623.kLq2Weys6P@polaris \
    --to=ebotcazou@adacore.com \
    --cc=Richard.Earnshaw@foss.arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ramana.radhakrishnan@foss.arm.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).