public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/48674] [4.7 Regression] FAIL: g++.dg/torture/pr48661.C
Date: Mon, 02 May 2011 13:48:00 -0000	[thread overview]
Message-ID: <bug-48674-4-1nY0cUa17H@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48674-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48674

--- Comment #6 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-05-02 13:47:47 UTC ---
> --- Comment #4 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-05-02 13:23:41 UTC ---

> Yes, the noise is annoying but I can't do anything but paper over the issue
> by either reverting the patch, reverting the testcase or trying to be
> clever with not exposing direct calls to thunks (which will trivially
> break with LTO and then, as now, continue to create wrong-code or ICE).

Fine with me: at this point, I'd like to avoid xfailing/skipping
testcases to make sure they aren't forgotten.  I'd just like to make
sure that the amount of noise doesn't get too big.

    Rainer


  parent reply	other threads:[~2011-05-02 13:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18 23:31 [Bug middle-end/48674] New: " hjl.tools at gmail dot com
2011-04-18 23:34 ` [Bug middle-end/48674] " hjl.tools at gmail dot com
2011-04-19  6:43 ` jakub at gcc dot gnu.org
2011-04-19  9:49 ` rguenth at gcc dot gnu.org
2011-05-02 13:03 ` ro at gcc dot gnu.org
2011-05-02 13:36 ` rguenth at gcc dot gnu.org
2011-05-02 13:48 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2011-05-02 13:49 ` rguenth at gcc dot gnu.org
2011-05-02 14:28 ` rguenth at gcc dot gnu.org
2011-05-02 14:56 ` hubicka at gcc dot gnu.org
2011-05-02 15:02 ` hubicka at gcc dot gnu.org
2011-05-02 15:10 ` rguenth at gcc dot gnu.org
2011-05-02 15:38 ` hubicka at gcc dot gnu.org
2011-05-14 12:57 ` dominiq at lps dot ens.fr
2011-08-02 14:08 ` 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-48674-4-1nY0cUa17H@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).