public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/50156] in-tree CLooG is not picked up by toplevel configure
Date: Tue, 30 Dec 2014 12:42:00 -0000 [thread overview]
Message-ID: <bug-50156-4-xzXwV9mp7o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50156-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50156
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |manu at gcc dot gnu.org
Resolution|--- |WONTFIX
--- Comment #4 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
CLooG will be removed in GCC 5.0. If you still think these patches are useful
for trunk please re-open the bug.
Patches in bugzilla tend to get lost, it is better to send them to gcc-patches@
and ping, ping, ping, ping... until you get someone to review them.
>From gcc-bugs-return-471927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 30 12:53:45 2014
Return-Path: <gcc-bugs-return-471927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10939 invoked by alias); 30 Dec 2014 12:53:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10883 invoked by uid 48); 30 Dec 2014 12:53:31 -0000
From: "belagod at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64443] New: New std::string implementation breaks tests on AArch64.
Date: Tue, 30 Dec 2014 12:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: belagod at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-64443-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-12/txt/msg02934.txt.bz2
Content-length: 3422
https://gcc.gnu.org/bugzilla/show_bug.cgi?idd443
Bug ID: 64443
Summary: New std::string implementation breaks tests on
AArch64.
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: belagod at gcc dot gnu.org
This commit seems to be breaking libstdc++-v3 runs on AArch64.
Author: redi <redi@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Fri Dec 19 18:16:39 2014 +0000
New std::string implementation.
* acinclude.m4 (GLIBCXX_ENABLE_LIBSTDCXX_CXX11_ABI): Remove.
(GLIBCXX_ENABLE_LIBSTDCXX_DUAL_ABI, GLIBCXX_DEFAULT_ABI): Add.
* configure.ac: Use new macros.
* configure: Regenerate.
* Makefile.in: Regenerate.
* doc/Makefile.in: Regenerate.
* libsupc++/Makefile.in: Regenerate.
* po/Makefile.in: Regenerate.
* src/Makefile.in: Regenerate.
* testsuite/Makefile.in: Regenerate.
* include/Makefile.am: Set _GLIBCXX_USE_DUAL_ABI.
* include/Makefile.in: Regenerate.
* config/abi/pre/gnu.ver: Export symbols related to new std::string.
Tighten old patterns to not match new symbols.
* config/locale/generic/monetary_members.cc: Guard some definitions
to not compile with new ABI.
* config/locale/gnu/monetary_members.cc: Likewise.
* config/locale/gnu/numeric_members.cc: Prevent double-free.
....
PASS->FAIL: 22_locale/locale/cons/6.cc execution test
PASS->FAIL: 22_locale/num_get/get/char/11.cc execution test
PASS->FAIL: 22_locale/num_get/get/char/12.cc execution test
PASS->FAIL: 22_locale/num_get/get/char/13.cc execution test
PASS->FAIL: 22_locale/num_get/get/char/14.cc execution test
PASS->FAIL: 22_locale/num_get/get/char/15.cc execution test
PASS->FAIL: 22_locale/num_get/get/char/22131.cc execution test
PASS->FAIL: 22_locale/num_get/get/char/23953.cc execution test
PASS->FAIL: 22_locale/num_get/get/char/37958.cc execution test
PASS->FAIL: 22_locale/num_get/get/char/39168.cc execution test
PASS->FAIL: 22_locale/num_get/get/wchar_t/11.cc execution test
PASS->FAIL: 22_locale/num_get/get/wchar_t/12.cc execution test
PASS->FAIL: 22_locale/num_get/get/wchar_t/13.cc execution test
PASS->FAIL: 22_locale/num_get/get/wchar_t/14.cc execution test
PASS->FAIL: 22_locale/num_get/get/wchar_t/15.cc execution test
PASS->FAIL: 22_locale/num_get/get/wchar_t/22131.cc execution test
PASS->FAIL: 22_locale/num_get/get/wchar_t/23953.cc execution test
PASS->FAIL: 22_locale/num_get/get/wchar_t/37958.cc execution test
PASS->FAIL: 22_locale/num_get/get/wchar_t/39168.cc execution test
PASS->FAIL: 22_locale/num_put/put/char/11.cc execution test
PASS->FAIL: 22_locale/num_put/put/char/23953.cc execution test
PASS->FAIL: 22_locale/num_put/put/char/38196.cc execution test
PASS->FAIL: 22_locale/num_put/put/wchar_t/11.cc execution test
PASS->FAIL: 22_locale/num_put/put/wchar_t/23953.cc execution test
PASS->FAIL: 22_locale/num_put/put/wchar_t/38196.cc execution test
PASS->FAIL: 22_locale/numpunct/members/char/cache_1.cc execution test
PASS->FAIL: 22_locale/numpunct/members/char/cache_2.cc execution test
PASS->FAIL: 22_locale/numpunct/members/wchar_t/cache_1.cc execution test
PASS->FAIL: 22_locale/numpunct/members/wchar_t/cache_2.cc execution test
prev parent reply other threads:[~2014-12-30 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 19:08 [Bug bootstrap/50156] New: " vanboxem.ruben at gmail dot com
2011-08-22 19:08 ` [Bug bootstrap/50156] " vanboxem.ruben at gmail dot com
2011-08-24 19:29 ` vanboxem.ruben at gmail dot com
2011-08-24 20:48 ` vanboxem.ruben at gmail dot com
2014-12-30 12:37 ` manu at gcc dot gnu.org
2014-12-30 12:42 ` manu at gcc dot gnu.org [this message]
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-50156-4-xzXwV9mp7o@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).