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 tree-optimization/49724] [4.6/4.7 Regression] FAIL: gnat.dg/socket1.adb execution test Date: Thu, 14 Jul 2011 09:14:00 -0000 [thread overview] Message-ID: <bug-49724-4-NRByIvZgGM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49724-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49724 --- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-07-14 09:13:19 UTC --- Based on Martin's comment in the other PR, I wonder whether this isn't rather a temporary failure because of a glitch on the host. Can you reproduce it?
next prev parent reply other threads:[~2011-07-14 9:14 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-13 1:35 [Bug ada/49724] New: " danglin at gcc dot gnu.org 2011-07-13 8:25 ` [Bug ada/49724] " rguenth at gcc dot gnu.org 2011-07-14 8:40 ` [Bug tree-optimization/49724] " ebotcazou at gcc dot gnu.org 2011-07-14 9:14 ` ebotcazou at gcc dot gnu.org [this message] 2011-07-14 11:55 ` dave.anglin at bell dot net 2011-07-16 16:40 ` danglin 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-49724-4-NRByIvZgGM@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).