public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ka_bena at yahoo dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/67930] segmentation fault Date: Tue, 13 Oct 2015 14:33:00 -0000 [thread overview] Message-ID: <bug-67930-4-jUFEnwOHhJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67930-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67930 --- Comment #2 from BENAÏSSA <ka_bena at yahoo dot fr> --- Thank you for your reply. Comments:: I am not convinced by your point of view. 1- the compilation step does not deliver any message. 2- I modify the string by address and this is permitted by C for any entity not private in its context. 3- if the compiler gcc allows segmentation fault for basic operations on pointers, I think that this is a severe bug and in consequence the compiler must be modified to remedie for such situations. This is my point of view. A.Benaïssa Le Lundi 12 octobre 2015 13h16, mpolacek at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org> a écrit : https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67930 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |mpolacek at gcc dot gnu.org Resolution|--- |INVALID --- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> --- You're trying to modify a string literal. That's no-no. >From gcc-bugs-return-499470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Oct 13 14:43:34 2015 Return-Path: <gcc-bugs-return-499470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 84147 invoked by alias); 13 Oct 2015 14:43:34 -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 84124 invoked by uid 48); 13 Oct 2015 14:43:30 -0000 From: "Pidgeot18 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/67937] gcov gives wrong results when negative counts are involved Date: Tue, 13 Oct 2015 14:43:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: gcov-profile X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: Pidgeot18 at gmail 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: Message-ID: <bug-67937-4-cMpFqNwyJR@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-67937-4@http.gcc.gnu.org/bugzilla/> References: <bug-67937-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-10/txt/msg01025.txt.bz2 Content-length: 331 https://gcc.gnu.org/bugzilla/show_bug.cgi?idg937 --- Comment #4 from Joshua Cranmer <Pidgeot18 at gmail dot com> --- (In reply to Richard Biener from comment #3) > Most interesting would be a C testcase that produces the CFG with the bogus > counters ;) Yeah, I know, but doing the minimization on a 5MLOC program takes time.
next prev parent reply other threads:[~2015-10-13 14:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-12 11:46 [Bug c/67930] New: " ka_bena at yahoo dot fr 2015-10-12 12:16 ` [Bug c/67930] " mpolacek at gcc dot gnu.org 2015-10-13 14:33 ` ka_bena at yahoo dot fr [this message] 2015-10-13 14:46 ` 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-67930-4-jUFEnwOHhJ@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).