public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/64813] [5 Regression] 23_containers/unordered_map/requirements/explicit_instantiation/[2,4].cc iCEs
Date: Wed, 11 Feb 2015 13:34:00 -0000	[thread overview]
Message-ID: <bug-64813-4-xDJ9JveFeG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64813-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #21 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Wed Feb 11 13:33:47 2015
New Revision: 220616

URL: https://gcc.gnu.org/viewcvs?rev=220616&root=gcc&view=rev
Log:
Handle noreturn function thunk creation.

    PR ipa/64813
    * cgraphunit.c (cgraph_node::expand_thunk): Do not create
    a return value for call to a function that is noreturn.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/cgraphunit.c
>From gcc-bugs-return-476848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 11 13:36:06 2015
Return-Path: <gcc-bugs-return-476848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8903 invoked by alias); 11 Feb 2015 13:36:06 -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 8814 invoked by uid 55); 11 Feb 2015 13:36:03 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65017] valgrind error in  get_constraint_for_address_of
Date: Wed, 11 Feb 2015 13:36: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65017-4-B6Au0vEg1e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65017-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65017-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-02/txt/msg01181.txt.bz2
Content-length: 1064

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

--- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 11 Feb 2015, dcb314 at hotmail dot com wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?ide017
>
> --- Comment #3 from David Binderman <dcb314 at hotmail dot com> ---
> (In reply to Richard Biener from comment #2)
> > I can't reproduce this - how did you compile/configure GCC?  Just tried both
> > --enable-checking and --enable-checking=release builds.
>
> ../src/trunk/configure --prefix=/home/dcb/gcc/results \
>     --disable-bootstrap \
>     --disable-werror \
>     --enable-checking=yes \
>     --enable-languages=c,c++,fortran \
>     CC="clang -fheinous-gnu-extensions" \
>     CXX="clang++ -fheinous-gnu-extensions"
>
> on AMD Phenom.

Uh, so it might be very well clang miscompiling it.  I don't have
clang to reproduce, so can you get me some more information,
like

(gdb) p debug_tree (t)

at the point it barfs?  Can you disable optimization of clang?
Thus build with CFLAGS="-g -O0" CXXFLAGS="-g -O0"?


  parent reply	other threads:[~2015-02-11 13:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  3:47 [Bug libstdc++/64813] New: 23_containers/unordered_map/requirements/explicit_instantiation/[2,4].cc iCEsA howarth at bromo dot med.uc.edu
2015-01-27  3:51 ` [Bug libstdc++/64813] " howarth at bromo dot med.uc.edu
2015-01-27 10:58 ` [Bug libstdc++/64813] 23_containers/unordered_map/requirements/explicit_instantiation/[2,4].cc iCEs redi at gcc dot gnu.org
2015-01-27 11:21 ` dominiq at lps dot ens.fr
2015-01-27 11:34 ` redi at gcc dot gnu.org
2015-01-27 18:12 ` howarth at bromo dot med.uc.edu
2015-01-27 19:56 ` [Bug tree-optimization/64813] " dominiq at lps dot ens.fr
2015-01-27 20:29 ` dominiq at lps dot ens.fr
2015-01-28 13:01 ` dominiq at lps dot ens.fr
2015-01-28 13:06 ` [Bug ipa/64813] " dominiq at lps dot ens.fr
2015-01-28 13:08 ` dominiq at lps dot ens.fr
2015-01-28 19:16 ` [Bug ipa/64813] [5 Regression] " dominiq at lps dot ens.fr
2015-01-30 14:11 ` marxin at gcc dot gnu.org
2015-01-31 16:42 ` danglin at gcc dot gnu.org
2015-02-02 18:10 ` hubicka at gcc dot gnu.org
2015-02-05 16:47 ` howarth at bromo dot med.uc.edu
2015-02-09  0:07 ` pinskia at gcc dot gnu.org
2015-02-09 13:29 ` dominiq at lps dot ens.fr
2015-02-09 13:58 ` dominiq at lps dot ens.fr
2015-02-09 17:35 ` dominiq at lps dot ens.fr
2015-02-11 13:34 ` marxin at gcc dot gnu.org [this message]
2015-02-11 14:07 ` marxin at gcc dot gnu.org
2015-03-23 10:18 ` yroux 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-64813-4-xDJ9JveFeG@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).