public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Glisse <marc.glisse@inria.fr>
To: William Tambe <tambewilliam@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Unconditional trap
Date: Sat, 12 Sep 2020 22:26:56 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.23.453.2009122225550.5239@stedding.saclay.inria.fr> (raw)
In-Reply-To: <CAF8i9mMheO7_RpnuY=h+zMe1DTun90J=VuBjdnNdc0ozRSs2qA@mail.gmail.com>

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?

-- 
Marc Glisse

  reply	other threads:[~2020-09-12 20:26 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 [this message]
2020-09-12 21:04   ` William Tambe
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=alpine.DEB.2.23.453.2009122225550.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).