public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/49825] [4.7 Regression] Many testcase failures Date: Sun, 24 Jul 2011 10:35:00 -0000 [thread overview] Message-ID: <bug-49825-4-1cH33ekdsr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49825-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49825 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ebotcazou at gcc dot | |gnu.org Target Milestone|--- |4.7.0 --- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-07-24 10:35:14 UTC --- FWIW we have the same pattern with our internal testing, i.e. essentially clean except at -Os with failures of the form: ================ Bug E318-012 ---------------- unexpected output +===========================GNAT BUG DETECTED==============================+ | Pro 6.5.0w (20110723-head) (i686-pc-linux-gnu) GCC error: | | in maybe_record_trace_start, at dwarf2cfi.c:2433 | | Error detected around btest.adb:66:8
next prev parent reply other threads:[~2011-07-24 10:35 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-23 21:21 [Bug middle-end/49825] New: [4.7 Regression] FAIL: g++.dg/tree-prof/partition2.C hjl.tools at gmail dot com 2011-07-23 23:16 ` [Bug middle-end/49825] [4.7 Regression] Many testcase failures hjl.tools at gmail dot com 2011-07-24 2:47 ` rth at gcc dot gnu.org 2011-07-24 10:35 ` ebotcazou at gcc dot gnu.org [this message] 2011-07-25 3:05 ` [Bug debug/49825] " rth at gcc dot gnu.org 2011-07-25 3:27 ` rth at gcc dot gnu.org 2011-07-25 4:36 ` rth at gcc dot gnu.org 2011-07-25 19:26 ` mikpe at it dot uu.se
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-49825-4-1cH33ekdsr@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: linkBe 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).