public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/47841] [4.6 Regression] New guality test failures
Date: Mon, 21 Feb 2011 19:20:00 -0000	[thread overview]
Message-ID: <bug-47841-4-BaphDqIVNe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47841-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-02-21 19:02:10 UTC ---
Saying these are regressions is weird, -flto has pretty much broken -g support
and lots of guality tests don't FAIL just because of being flagged as
UNSUPPORTED (as the tests conservatively assume some of the errors might be gdb
bugs).


  parent reply	other threads:[~2011-02-21 19:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 18:58 [Bug lto/47841] New: " hjl.tools at gmail dot com
2011-02-21 19:02 ` [Bug lto/47841] " hjl.tools at gmail dot com
2011-02-21 19:20 ` jakub at gcc dot gnu.org [this message]
2011-02-22  9:27 ` jakub at gcc dot gnu.org
2011-02-22  9:53 ` rguenth at gcc dot gnu.org
2011-02-22 10:10 ` jakub at gcc dot gnu.org
2011-03-25 20:06 ` [Bug lto/47841] [4.6/4.7 " jakub at gcc dot gnu.org
2011-06-27 15:47 ` jakub at gcc dot gnu.org
2011-10-26 17:40 ` jakub at gcc dot gnu.org
2012-03-01 15:47 ` jakub at gcc dot gnu.org
2012-05-07 12:24 ` [Bug lto/47841] [4.6/4.7/4.8 " 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-47841-4-BaphDqIVNe@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).