public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "masmiseim at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108283] Problem when accessing address zero Date: Wed, 04 Jan 2023 11:47:25 +0000 [thread overview] Message-ID: <bug-108283-4-4V4k6oAAql@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108283-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108283 Markus <masmiseim at gmx dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |--- --- Comment #4 from Markus <masmiseim at gmx dot de> --- Hello Andrew, thanks for the feedback. Using an mmu respectively working on application-level on an OS like Linux is as far as I know the only exception on ARM devices where zero is not a valid address from target point of view. For example, compare the Technical Reference Manual of the Cortex M7 (https://developer.arm.com/documentation/ddi0489/f/programmers-model/system-address-map?lang=en) in Chapter ‘System address map’ is defined that the complete address range from 0x0 to 0x1FFFFFFF is reserved for Code Memory. Why not set the -fdelete-null-pointer-checks option also for ARM Targets like it is done for AVR, MSP430? Wouldn't it be better to generate a warning instead? If this is not possible, why not creating a warning in addition to the special-null-pointer handling. As a user I’m not aware of every switch and option of the compiler. Therefore, it was not obvious that this was an intentional behaviour of the compiler and not a bug. Especially since CLANG worked here as I would expect it to. Regards
next prev parent reply other threads:[~2023-01-04 11:47 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-04 10:20 [Bug target/108283] New: " masmiseim at gmx dot de 2023-01-04 10:24 ` [Bug target/108283] " pinskia at gcc dot gnu.org 2023-01-04 10:28 ` pinskia at gcc dot gnu.org 2023-01-04 10:29 ` pinskia at gcc dot gnu.org 2023-01-04 11:47 ` masmiseim at gmx dot de [this message] 2023-01-04 13:47 ` pinskia at gcc dot gnu.org 2023-01-04 13:51 ` pinskia at gcc dot gnu.org 2023-01-04 14:33 ` jakub at gcc dot gnu.org 2023-01-04 15:31 ` masmiseim at gmx dot de 2023-01-04 15:57 ` jakub at gcc dot gnu.org
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=bug-108283-4-4V4k6oAAql@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).