public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Jeff Law <law@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Fix for PRs 36043, 58744 and 65408
Date: Wed, 18 Mar 2015 04:22:00 -0000	[thread overview]
Message-ID: <20150318042208.GD24573@bubble.grove.modra.org> (raw)
In-Reply-To: <55088069.3010802@redhat.com>

On Tue, Mar 17, 2015 at 01:28:41PM -0600, Jeff Law wrote:
> On 03/14/2015 07:02 AM, Alan Modra wrote:
> >	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.
> I think this is probably a stage1 item.  Richi, Jakub, Joseph, do any of you
> think we should try to push this into gcc-5?

Some (severity) background to PR65408.  The bug came from SAP HANA
(en.wikipedia.org/wiki/SAP_HANA), a crash that happens on powerpc64
and powerpc64le.  aarch64 would also be susceptible to the crash since
it also loads 16 bytes for the 12-byte struct.  x86_64 only loads 12
bytes (i386.c:construct_container generates a parallel with a DImode
and SImode load).  However the underlying bug is there and hits x86_64
too for the pr58744 and pr36043 testcases..

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2015-03-18  4:22 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
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 [this message]
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=20150318042208.GD24573@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@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).