public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vq at larryv dot me" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/63810] gcc sets incorrect macro for OS X deployment targets Date: Wed, 20 May 2015 22:01:00 -0000 [thread overview] Message-ID: <bug-63810-4-4XJK2I2NNU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63810-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63810 --- Comment #25 from Lawrence Velázquez <vq at larryv dot me> --- (In reply to mrs@gcc.gnu.org from comment #22) > Though I approved it on list, you should feel free to update with the review > points others have and post that version if you wish. Re-roll posted: https://gcc.gnu.org/ml/gcc-patches/2015-05/msg01888.html >From gcc-bugs-return-486861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 20 22:05:39 2015 Return-Path: <gcc-bugs-return-486861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 67125 invoked by alias); 20 May 2015 22:05:39 -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 66400 invoked by uid 48); 20 May 2015 22:05:36 -0000 From: "gpnuma at centaurean dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/66230] New: Using optimizations causes program to segfault Date: Wed, 20 May 2015 22:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 4.9.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: gpnuma at centaurean dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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 target_milestone Message-ID: <bug-66230-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: 2015-05/txt/msg01701.txt.bz2 Content-length: 1309 https://gcc.gnu.org/bugzilla/show_bug.cgi?idf230 Bug ID: 66230 Summary: Using optimizations causes program to segfault Product: gcc Version: 4.9.2 Status: UNCONFIRMED Severity: major Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gpnuma at centaurean dot com Target Milestone: --- Hello, First I'd like to point out that the code producing this error compiles and runs fine in gcc 4.8.4-1 for Linux and OS/X and Clang 3.5, 3.6 (Linux) and 6.1 (OS/X), but fails with gcc 4.9.2 when using -O3 on both Linux and OS/X (in debug mode it works fine). The platform used for all these tests was x86_64. To reproduce : clone and build https://github.com/centaurean/density with gcc 4.9.2. Then run the following command : ./benchmark -3 some_file This will turn into a segfault. When I add the line [printf("anything");] just before DENSITY_MEMCPY(... here : https://github.com/centaurean/density/blob/master/src/kernel_lion_decode.c#L187, the program runs again normally without any segfault... that's really super strange. The function that fails is called via an array of function pointers, but I don't think that's the problem since it works with any other compiler.
next prev parent reply other threads:[~2015-05-20 22:01 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-11 2:00 [Bug driver/63810] New: " jeremyhu at macports dot org 2014-11-11 7:38 ` [Bug target/63810] " fxcoudert at gcc dot gnu.org 2014-11-14 9:09 ` larryv at macports dot org 2014-11-14 9:16 ` larryv at macports dot org 2014-11-14 21:21 ` howarth at bromo dot med.uc.edu 2014-11-14 21:24 ` larryv at macports dot org 2014-11-14 21:59 ` larryv at macports dot org 2014-11-18 6:40 ` larryv at macports dot org 2014-11-18 7:31 ` larryv at macports dot org 2014-11-18 9:32 ` fxcoudert at gcc dot gnu.org 2014-12-22 22:42 ` egall at gwmail dot gwu.edu 2015-05-15 6:54 ` vq at larryv dot me 2015-05-15 22:52 ` fxcoudert at gcc dot gnu.org 2015-05-16 2:16 ` vq at larryv dot me 2015-05-16 7:58 ` fxcoudert at gcc dot gnu.org 2015-05-20 22:01 ` vq at larryv dot me [this message] 2015-05-28 12:27 ` mrs at gcc dot gnu.org 2015-05-28 16:08 ` vq at larryv dot me
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-63810-4-4XJK2I2NNU@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).