From: Alan Modra <amodra@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Fix for PRs 36043, 58744 and 65408
Date: Sat, 14 Mar 2015 13:55:00 -0000 [thread overview]
Message-ID: <20150314135531.GE16488@bubble.grove.modra.org> (raw)
In-Reply-To: <CAMe9rOqScLv2e3HKoxxdOJfWnRcpbY9j3xHKrTb_pHdLYwGjww@mail.gmail.com>
On Sat, Mar 14, 2015 at 06:14:40AM -0700, H.J. Lu wrote:
> On Sat, Mar 14, 2015 at 6:02 AM, Alan Modra <amodra@gmail.com> wrote:
> > 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?
>
> Can you add a testcase in
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36043
I was thinking that mmap/munmap is less portable than sbrk. Hmm, a
grep over the testsuite says mmap is already used and
do-do run { target mmap } is available. OK, I'm happy to jump that
way too.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2015-03-14 13:55 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 [this message]
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=20150314135531.GE16488@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.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).