public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/61143] [4.9/4.10 Regression] Arithmetic exception on emplacing into unordered_map moved out
Date: Sun, 11 May 2014 11:02:00 -0000	[thread overview]
Message-ID: <bug-61143-4-OFvjRAYdBQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61143-4@http.gcc.gnu.org/bugzilla/>

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

Daniel Krügler <daniel.kruegler at googlemail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daniel.kruegler@googlemail.
                   |                            |com

--- Comment #2 from Daniel Krügler <daniel.kruegler at googlemail dot com> ---
The problem also occurs in gcc 4.10 trunk and I can confirm that this wasn't
the case for 4.7.3, 4.8.1, 4.8.2.
>From gcc-bugs-return-451247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 11 12:28:55 2014
Return-Path: <gcc-bugs-return-451247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21735 invoked by alias); 11 May 2014 12:28:54 -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 21449 invoked by uid 48); 11 May 2014 12:28:46 -0000
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/25672] [4.7/4.8/4.9/4.10 Regression] cross build's libgcc picks up CFLAGS
Date: Sun, 11 May 2014 12:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 4.1.0
X-Bugzilla-Keywords: build, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: olegendo at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-25672-4-krLwy6ZQ0b@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-25672-4@http.gcc.gnu.org/bugzilla/>
References: <bug-25672-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-05/txt/msg00939.txt.bz2
Content-length: 859

http://gcc.gnu.org/bugzilla/show_bug.cgi?id%672

Oleg Endo <olegendo at gcc dot gnu.org> changed:

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

--- Comment #35 from Oleg Endo <olegendo at gcc dot gnu.org> ---
Just ran into the same issue with trunk r210305, while building a cross SH on
OSX.  The newly merged wide-int code contains some things, which clang
considers an error.  Setting
export CFLAGS="-fheinous-gnu-extensions"
export CXXFLAGS="-fheinous-gnu-extensions"

fixes that, but then one need also to set e.g.
export CFLAGS_FOR_TARGET="-O2"
export CXXFLAGS_FOR_TARGET="-O2"

or else -fheinous-gnu-extensions will be passed to the xgcc.
This really should be documented somewhere...


  parent reply	other threads:[~2014-05-11 11:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-10 23:46 [Bug libstdc++/61143] New: " felix at fontein dot de
2014-05-11  7:30 ` [Bug libstdc++/61143] " felix at fontein dot de
2014-05-11 10:03 ` [Bug libstdc++/61143] [4.9/4.10 Regression] " redi at gcc dot gnu.org
2014-05-11 11:02 ` daniel.kruegler at googlemail dot com [this message]
2014-05-11 14:06 ` redi at gcc dot gnu.org
2014-05-12  6:43 ` fdumont at gcc dot gnu.org
2014-05-12 10:01 ` redi at gcc dot gnu.org
2014-05-12 10:07 ` glisse at gcc dot gnu.org
2014-05-13  9:19 ` redi at gcc dot gnu.org
2014-05-13  9:32 ` redi at gcc dot gnu.org
2014-05-13 15:26 ` felix at fontein dot de
2014-05-13 20:14 ` fdumont at gcc dot gnu.org
2014-05-13 20:48 ` redi at gcc dot gnu.org
2014-05-21 19:51 ` fdumont at gcc dot gnu.org
2014-05-23 19:35 ` fdumont 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-61143-4-OFvjRAYdBQ@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).