public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bernhard.kaindl at thalesgroup dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/48181] [4.8/4.9 Regression] wrong code with -O -fgcse --param ira-max-conflict-table-size=0 Date: Wed, 10 Jun 2015 00:49:00 -0000 [thread overview] Message-ID: <bug-48181-4-zULnrbXn4D@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48181-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48181 Bernhard Kaindl <bernhard.kaindl at thalesgroup dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhard.kaindl@thalesgroup | |.com --- Comment #11 from Bernhard Kaindl <bernhard.kaindl at thalesgroup dot com> --- Checked what Steven Bosscher said in comment #5 and what I understood from Comment 6 that LRA fixed this issue: > FWIW I can't reproduce the problem with trunk. I see rcx being saved > and restored around the calls, e.g.: > > movq %rcx, (%rsp) > call bar > movq (%rsp), %rcx > > and likewise around the second memcpy. Unfortunately (an old) valgrind > on gcc17 doesn't work with with "valgrind -q ./a.out" as in comment #0. > http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=192719 > fixed this (so, most likely reproduceable by disabling LRA). Indeed, gcc-4.8.4 and gcc-4.9.2 save and restore rcx as described, valgrind-3.10.1 (current release) does not show an error, and program does not crash at all. So affected are only gcc-4.5, 4.6 and 4.7, and only with --param ira-max-conflict-table-size=0 & -fgcse active.
next prev parent reply other threads:[~2015-06-10 0:49 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-18 14:40 [Bug rtl-optimization/48181] New: [4.5/4.6/4.7 " zsojka at seznam dot cz 2011-03-18 14:51 ` [Bug rtl-optimization/48181] " rguenth at gcc dot gnu.org 2011-03-22 0:54 ` steven at gcc dot gnu.org 2011-04-10 10:43 ` rguenth at gcc dot gnu.org 2011-04-28 15:00 ` rguenth at gcc dot gnu.org 2012-07-02 11:08 ` [Bug rtl-optimization/48181] [4.5/4.6/4.7/4.8 " rguenth at gcc dot gnu.org 2013-01-08 15:17 ` [Bug rtl-optimization/48181] [4.6/4.7/4.8 " jakub at gcc dot gnu.org 2013-01-16 22:49 ` steven at gcc dot gnu.org 2013-01-16 23:08 ` jakub at gcc dot gnu.org 2013-04-12 15:17 ` [Bug rtl-optimization/48181] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2014-06-12 13:47 ` [Bug rtl-optimization/48181] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:29 ` [Bug rtl-optimization/48181] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-03-24 10:46 ` [Bug rtl-optimization/48181] [4.8/4.9 " steven at gcc dot gnu.org 2015-06-10 0:49 ` bernhard.kaindl at thalesgroup dot com [this message] 2015-06-10 1:28 ` bernhard.kaindl at thalesgroup dot com 2015-06-10 9:05 ` [Bug rtl-optimization/48181] " rguenth 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-48181-4-zULnrbXn4D@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).