From: Marc Glisse <marc.glisse@inria.fr>
To: William Tambe <tambewilliam@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Unconditional trap
Date: Sat, 12 Sep 2020 23:24:35 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.23.453.2009122313280.5239@stedding.saclay.inria.fr> (raw)
In-Reply-To: <CAF8i9mNoT1MvhJCg0LdYh4WxxBGMMVfOjiANAXBWtsFdT7R3Fw@mail.gmail.com>
On Sat, 12 Sep 2020, William Tambe via Gcc-help wrote:
> Using -fno-delete-null-pointer-checks helps.
>
> Is there a way to make it permanent in the GCC source such that
> providing that option is not needed ?
$ grep -R delete-null-pointer-checks gcc/config
gcc/config/nios2/elf.h:/* Default -fdelete-null-pointer-checks to off, to prevent the compiler
gcc/config/cr16/cr16.c: /* Disable -fdelete-null-pointer-checks option for CR16 target.
TARGET_OPTION_OVERRIDE seems to be the way if you want to disable it for
some specific target. If you want to change the default for all targets,
you could edit common.opt instead.
--
Marc Glisse
next prev parent reply other threads:[~2020-09-12 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 20:17 William Tambe
2020-09-12 20:26 ` Marc Glisse
2020-09-12 21:04 ` William Tambe
2020-09-12 21:24 ` Marc Glisse [this message]
2020-09-13 14:11 ` Segher Boessenkool
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=alpine.DEB.2.23.453.2009122313280.5239@stedding.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc-help@gcc.gnu.org \
--cc=tambewilliam@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).