public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "soren.brinkmann at xilinx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/67651] Optimizer assumes nothing can reside at address 0 despite -fno-delete-null-pointer-checks
Date: Sun, 20 Sep 2015 16:19:00 -0000	[thread overview]
Message-ID: <bug-67651-4-BnJAxdWuJh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67651-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67651

--- Comment #1 from Sören Brinkmann <soren.brinkmann at xilinx dot com> ---
Created attachment 36352
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36352&action=edit
Makefile for the test case
>From gcc-bugs-return-497614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Sep 20 16:29:19 2015
Return-Path: <gcc-bugs-return-497614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33281 invoked by alias); 20 Sep 2015 16:29:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33242 invoked by uid 48); 20 Sep 2015 16:29:15 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67650] undef reference with -fdevirtualize
Date: Sun, 20 Sep 2015 16:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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:
Message-ID: <bug-67650-4-OVVXzeGz61@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67650-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67650-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg01592.txt.bz2
Content-length: 380

https://gcc.gnu.org/bugzilla/show_bug.cgi?idg650

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> Is it worth it to try reducing my code and produce a code snippet exhibiting the issue?

Always.

>Or is the issue known already? I didn't find any track of it.

It could also be a bug in your code too.  Devirtualization is known to expose
invalid code too.


  reply	other threads:[~2015-09-20 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-20 16:14 [Bug c/67651] New: " soren.brinkmann at xilinx dot com
2015-09-20 16:19 ` soren.brinkmann at xilinx dot com [this message]
2015-09-21  8:06 ` [Bug middle-end/67651] " rguenth at gcc dot gnu.org
2015-09-21 12:33 ` rguenth at gcc dot gnu.org
2015-09-21 12:33 ` rguenth 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-67651-4-BnJAxdWuJh@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: 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).