From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E54543858C53; Wed, 4 Jan 2023 14:33:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E54543858C53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1672842820; bh=sd7coD9kzlOIIC0fm4cZPSsWFGf6DqY8PLZ+5WPPCyg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=gtdEHCpwJvaW2ep3JTE32T9pRH2RJFUVdxyW3ro6joJxPI/THI6rFYMpxNuzYwHhO PvJIDMsxCb0wXr/BJ7o948Lq0ez5yAaWChhDHH78E03c+wGJvUcK0Ndb27sNAeGd4w +IpGdoEZb82NryHido2RSMwX0VTOtEN8T7hPa7ME= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108283] Problem when accessing address zero Date: Wed, 04 Jan 2023 14:33:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108283 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #7 from Jakub Jelinek --- And the fact that one can access object at address 0 doesn't mean it is wis= e to put there any object, because valid C/C++ can't do that, so if you really n= eed something to be there, special care needs to be used to hide that from the compiler.=