public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Fix for PRs 36043, 58744 and 65408
Date: Sat, 14 Mar 2015 13:14:00 -0000	[thread overview]
Message-ID: <CAMe9rOqScLv2e3HKoxxdOJfWnRcpbY9j3xHKrTb_pHdLYwGjww@mail.gmail.com> (raw)
In-Reply-To: <20150314130238.GD16488@bubble.grove.modra.org>

On Sat, Mar 14, 2015 at 6:02 AM, Alan Modra <amodra@gmail.com> wrote:
> This is Richi's prototype patch in
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36043#c23 with fixes for
> blocks larger than one reg, big-endian, and BLOCK_REG_PADDING.
> I also removed the operand_subword_force since we may as well let
> narrow_bit_field_mem in extract_bit_field do that for us.  It is
> necessary to do the BLOCK_REG_PADDING shift after we've loaded the
> block or else repeat the bit-field extraction in that case.
>
> Bootstrapped and regression tested (-m32 and -m64) x86_64-linux and
> powerpc64-linux.  OK to apply?
>
> I'll also throw together a testcase or three.  For execute tests I'm
> thinking of using sbrk to locate an odd sized struct such that access
> past the end segfaults, rather than mmap/munmap as was done in the
> pr36043 testcase.  Does that sound reasonable?
>
>         PR target/65408
>         PR target/58744
>         PR middle-end/36043
>         * calls.c (load_register_parameters): Don't load past end of
>         mem unless suitably aligned.
>

Can you add a testcase in

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36043


-- 
H.J.

  reply	other threads:[~2015-03-14 13:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-14 13:02 Alan Modra
2015-03-14 13:14 ` H.J. Lu [this message]
2015-03-14 13:55   ` Alan Modra
2015-03-14 13:58 ` Bernhard Reutner-Fischer
2015-03-14 17:52   ` Mike Stump
2015-03-14 17:56     ` Jakub Jelinek
2015-03-14 18:28       ` Mike Stump
2015-03-15  3:00 ` Alan Modra
2015-03-17 19:28 ` Jeff Law
2015-03-18  4:22   ` Alan Modra
2015-03-18 11:12     ` Richard Biener
2015-04-13  4:50       ` Alan Modra
2015-04-13  7:47         ` 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=CAMe9rOqScLv2e3HKoxxdOJfWnRcpbY9j3xHKrTb_pHdLYwGjww@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --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).