public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dodji at seketeli dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/54860] [4.8 Regression]: build fails when configuring libgfortran due to recent "attribute" changes in core gcc
Date: Tue, 09 Oct 2012 21:33:00 -0000 [thread overview]
Message-ID: <bug-54860-4-AMByxoOL5U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54860-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54860
--- Comment #15 from dodji at seketeli dot org <dodji at seketeli dot org> 2012-10-09 21:33:00 UTC ---
> --- Comment #13 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2012-10-09 20:43:11 UTC ---
>
> The patch fixes the problem for cris-elf with no regressions in test-suite
> results. Thanks!
You are welcome. Sorry for the breakage in the first place.
> But, the new tests introduce some new failures:
> +g++.sum g++.dg/cpp0x/gen-attrs-17.2.C
>
> +g++.sum g++.dg/cpp0x/gen-attrs-21.C
>
> +g++.sum g++.dg/cpp0x/gen-attrs-39.C
>
> +g++.sum g++.dg/cpp0x/gen-attrs-51.C
>
> +g++.sum g++.dg/cpp0x/gen-attrs-52.C
Hmmh. I don't reach the point of running testsuites on my limited
cross-compilation setup here. Would it be possible that I see the log
of these testsuite errors somehow?
Thank you.
next prev parent reply other threads:[~2012-10-09 21:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 20:49 [Bug middle-end/54860] New: [4.8 Regression]: build fails on cris-elf " hp at gcc dot gnu.org
2012-10-08 21:58 ` [Bug middle-end/54860] " dodji at gcc dot gnu.org
2012-10-08 22:23 ` dodji at seketeli dot org
2012-10-08 22:47 ` hp at gcc dot gnu.org
2012-10-09 1:50 ` hp at gcc dot gnu.org
2012-10-09 3:26 ` hp at gcc dot gnu.org
2012-10-09 6:37 ` ubizjak at gmail dot com
2012-10-09 7:56 ` [Bug middle-end/54860] [4.8 Regression]: build fails when " ubizjak at gmail dot com
2012-10-09 14:08 ` dodji at seketeli dot org
2012-10-09 14:52 ` dodji at gcc dot gnu.org
2012-10-09 16:41 ` davem at gcc dot gnu.org
2012-10-09 17:12 ` davem at gcc dot gnu.org
2012-10-09 18:40 ` ubizjak at gmail dot com
2012-10-09 20:43 ` hp at gcc dot gnu.org
2012-10-09 21:29 ` dodji at seketeli dot org
2012-10-09 21:33 ` dodji at seketeli dot org [this message]
2012-10-09 21:57 ` hp at gcc dot gnu.org
2012-10-09 22:02 ` hp at gcc dot gnu.org
2012-10-10 10:25 ` dodji at gcc dot gnu.org
2012-11-20 12:28 ` jakub at gcc dot gnu.org
2012-11-20 15:27 ` hp at gcc dot gnu.org
2012-11-20 18:17 ` hp 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-54860-4-AMByxoOL5U@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).