public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vhaisman at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/62200] libstdc++ initialization priority Date: Wed, 20 Aug 2014 10:05:00 -0000 [thread overview] Message-ID: <bug-62200-4-ItAS0rNtVA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62200-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62200 --- Comment #1 from Václav Zeman <vhaisman at gmail dot com> --- And it dumps core on Cygwin as well. >From gcc-bugs-return-458852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Aug 20 10:24:12 2014 Return-Path: <gcc-bugs-return-458852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 21453 invoked by alias); 20 Aug 2014 10:24:12 -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 21392 invoked by uid 48); 20 Aug 2014 10:24:09 -0000 From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/62132] [5 Regression] FAIL: c-c++-common/asan/misalign-[12].c after r213807 on x86_64-apple-darwin13 with -m32 Date: Wed, 20 Aug 2014 10:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-62132-4-Pham49JqlZ@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-62132-4@http.gcc.gnu.org/bugzilla/> References: <bug-62132-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-08/txt/msg01349.txt.bz2 Content-length: 569 https://gcc.gnu.org/bugzilla/show_bug.cgi?idb132 --- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Yury Gribov from comment #4) > Note that same problem may pop up in other tests as well so IMHO better fix > this in general. Well, we could switch frame pointers in the [darwin.h] asan spec, but I'm a bit inclined to leave this under User control and just accept that we need to keep an eye on test-cases. Will think some more about doing it automatically, but suggest that we immediately fix these cases for now with Dominique's patch.
next prev parent reply other threads:[~2014-08-20 10:05 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-20 10:02 [Bug libstdc++/62200] New: " vhaisman at gmail dot com 2014-08-20 10:05 ` vhaisman at gmail dot com [this message] 2023-02-03 19:49 ` [Bug libstdc++/62200] " pinskia 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-62200-4-ItAS0rNtVA@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).