From: Sandra Loosemore <sandra@codesourcery.com>
To: Richard Henderson <rth@redhat.com>
Cc: <gcc-patches@gcc.gnu.org>, <richard.guenther@gmail.com>
Subject: Re: [PATCH v2 08/13] Add TARGET_ADDR_SPACE_ZERO_ADDRESS_VALID
Date: Thu, 22 Oct 2015 03:27:00 -0000 [thread overview]
Message-ID: <56285402.9050001@codesourcery.com> (raw)
In-Reply-To: <1445376433-14658-9-git-send-email-rth@redhat.com>
On 10/20/2015 03:27 PM, Richard Henderson wrote:
>
> +@deftypefn {Target Hook} bool TARGET_ADDR_SPACE_ZERO_ADDRESS_VALID (addr_space_t @var{as})
> +Define this to modify the default handling of address 0 for the
> +address space. Return true if 0 should be considered a valid address.
> +@end deftypefn
> +
I'm confused by this new hook. How does it interact with
-fdelete-null-pointer-checks? E.g. nios2-elf defaults
flag_delete_null_pointer_checks to 0 precisely because address 0 is
legitimate on that target. The avr and cr16 backends simply override
flag_delete_null_pointer_checks. Do backends that already frob one
thing need to frob the other as well? Are there any changes to the user
documentation for -fdelete-null-pointer-checks required?
-Sandra
next prev parent reply other threads:[~2015-10-22 3:13 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 21:27 [PATCH v2 00/13] Address space support for x86 Richard Henderson
2015-10-20 21:28 ` [PATCH v2 02/13] Relax ADDR_SPACE_GENERIC_P checks for default address space hooks Richard Henderson
2015-10-21 14:02 ` Jeff Law
2015-10-21 20:50 ` Richard Henderson
2015-10-20 21:28 ` [PATCH v2 06/13] i386: Replace ix86_address_seg with addr_space_t Richard Henderson
2015-10-20 21:28 ` [PATCH v2 08/13] Add TARGET_ADDR_SPACE_ZERO_ADDRESS_VALID Richard Henderson
2015-10-21 13:59 ` Jeff Law
2015-10-21 20:51 ` Richard Henderson
2015-10-21 21:29 ` Jeff Law
2015-10-22 3:27 ` Sandra Loosemore [this message]
2015-10-22 7:59 ` Richard Biener
2015-10-23 17:08 ` Sandra Loosemore
2015-10-22 19:17 ` Richard Henderson
2015-10-20 21:28 ` [PATCH v2 10/13] Avoid CSE of MEMs in different address spaces Richard Henderson
2015-10-21 13:49 ` Jeff Law
2015-10-21 17:12 ` Richard Henderson
2015-10-22 7:48 ` Richard Biener
2015-10-20 21:28 ` [PATCH v2 07/13] i386: Add address space for tls Richard Henderson
2015-10-20 21:28 ` [PATCH v2 09/13] Fix PR 66768 Richard Henderson
2015-10-21 13:56 ` Jeff Law
2015-10-21 17:55 ` Richard Henderson
2015-10-20 21:28 ` [PATCH v2 01/13] Change default of non-overlapping address space conversion Richard Henderson
2015-10-21 14:03 ` Jeff Law
2015-10-20 21:28 ` [PATCH v2 05/13] i386: Add address spaces for fs/gs segments Richard Henderson
2015-10-20 21:28 ` [PATCH v2 04/13] i386: Disallow address spaces with string insns Richard Henderson
2015-10-20 21:28 ` [PATCH v2 11/13] Test case for conversion from __seg_tls:0 Richard Henderson
2015-11-09 14:46 ` Richard Biener
2015-11-09 17:55 ` Thomas Schwinge
2015-10-20 21:28 ` [PATCH v2 12/13] Document the x86 address spaces Richard Henderson
2015-10-22 4:59 ` Sandra Loosemore
2015-10-22 20:30 ` Richard Henderson
2015-10-23 17:16 ` Sandra Loosemore
2015-10-20 21:28 ` [PATCH v2 13/13] Add hook for modifying debug info for " Richard Henderson
2015-10-21 13:55 ` Jeff Law
2015-10-21 14:57 ` H.J. Lu
2015-10-21 17:23 ` Richard Henderson
2015-10-21 17:25 ` H.J. Lu
2015-10-21 17:51 ` Richard Henderson
2015-10-21 18:36 ` H.J. Lu
2015-10-21 16:22 ` Ulrich Weigand
2015-10-21 19:13 ` Richard Henderson
2015-10-22 14:19 ` Ulrich Weigand
2015-10-20 21:34 ` [PATCH v2 03/13] i386: Handle address spaces in movabs patterns Richard Henderson
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=56285402.9050001@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=rth@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).