public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: Alan Modra <amodra@gmail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, binutils <binutils@sourceware.org>
Subject: Re: [Patch] ld: check for address space overflow
Date: Wed, 15 Mar 2017 09:26:00 -0000	[thread overview]
Message-ID: <DEF550D7-44F0-42D4-8C20-F08C1D73D209@adacore.com> (raw)
In-Reply-To: <20170315011101.GN4983@bubble.grove.modra.org>


> On 15 Mar 2017, at 02:11, Alan Modra <amodra@gmail.com> wrote:
> 
> On Tue, Mar 14, 2017 at 02:56:18PM +0100, Tristan Gingold wrote:
>>    	* testsuite/ld-checks/checks.exp (overflow_check): Disable for
>>    	non-elf targets.
> 
> OK.

Thanks, committed.

>  I'm going to commit the following too.  h8300 and ip2k targets
> use a 16-bit address cpu by default, so hit the address wrap check
> (more than once) on the 64k section test.
> 
> 	* testsuite/ld-elf/sec64k.exp: Don't run on h8300 and ip2k.

Thank you for the head-up.
Maybe the overflow check should also check that the length is not larger than the address space (otherwise it could have missed these h8300 and ip2k cases), but I think this is a too artificial case.

Tristan.

  reply	other threads:[~2017-03-15  9:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 14:29 Tristan Gingold
2017-03-11  1:14 ` Alan Modra
2017-03-13  9:47   ` Tristan Gingold
2017-03-13 17:52     ` H.J. Lu
2017-03-13 19:06 ` H.J. Lu
2017-03-13 19:27   ` H.J. Lu
2017-03-14  8:15     ` Tristan Gingold
2017-03-14 10:20       ` Alan Modra
2017-03-14 10:50         ` Tristan Gingold
2017-03-14 12:17           ` Alan Modra
2017-03-14 13:56             ` Tristan Gingold
2017-03-15  1:11               ` Alan Modra
2017-03-15  9:26                 ` Tristan Gingold [this message]
2017-03-14 16:13       ` H.J. Lu

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=DEF550D7-44F0-42D4-8C20-F08C1D73D209@adacore.com \
    --to=gingold@adacore.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.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).