From: William Tambe <tambewilliam@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Unconditional trap
Date: Sat, 12 Sep 2020 16:04:23 -0500 [thread overview]
Message-ID: <CAF8i9mNoT1MvhJCg0LdYh4WxxBGMMVfOjiANAXBWtsFdT7R3Fw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.23.453.2009122225550.5239@stedding.saclay.inria.fr>
On Sat, Sep 12, 2020 at 3:26 PM Marc Glisse <marc.glisse@inria.fr> wrote:
>
> On Sat, 12 Sep 2020, William Tambe via Gcc-help wrote:
>
> > However it causes the compiler to generate a trap when address 0 is
> > used; in the example below, I have a function that prints characters
> > through the UART using address 0; but the resulting assembly generates
> > a function that traps instead.
>
> Are you using -fno-delete-null-pointer-checks?
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 ?
>
> --
> Marc Glisse
next prev parent reply other threads:[~2020-09-12 21:04 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 [this message]
2020-09-12 21:24 ` Marc Glisse
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=CAF8i9mNoT1MvhJCg0LdYh4WxxBGMMVfOjiANAXBWtsFdT7R3Fw@mail.gmail.com \
--to=tambewilliam@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/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).