--- Comment #8 from rguenth at gcc dot gnu dot org 2010-03-01 15:44 ---
Subject: Bug 41250
Author: rguenth
Date: Mon Mar 1 15:43:32 2010
New Revision: 157148
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=157148
Log:
2010-03-01 Richard Guenther
Martin Jambor
--- Comment #7 from rguenth at gcc dot gnu dot org 2010-03-01 15:43 ---
Fixed.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
Status|ASSIGNED
--- Comment #6 from rguenth at gcc dot gnu dot org 2010-03-01 13:14 ---
*** Bug 42805 has been marked as a duplicate of this bug. ***
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #5 from rguenth at gcc dot gnu dot org 2010-03-01 12:57 ---
Mine.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned
--- Comment #4 from sje at cup dot hp dot com 2010-02-26 19:05 ---
Was the patch from comment #3 ever sent to gcc-patches? I couldn't find it. I
did see earlier discussions about some other patches but the patch in comment
#3 seems to have been put here after those discussions.
I test
--- Comment #3 from jamborm at gcc dot gnu dot org 2009-10-05 13:22 ---
On IRC, Jakub told me to remove the value_expr flag after
gimplification and to introduce a new dummy var decl with the flag set
for the purpose of debugging. My first attempt is the following
patch. It did bootstr
--- Comment #2 from jamborm at gcc dot gnu dot org 2009-09-11 23:38 ---
I ran into too many problems when I tried to inhibit value_expr
PARM_DECL substitutions in the gimplifier. At the moment I believe we
should not use the value_expr just for debug info and rather try
BLOCK_NONLOCALIZ
--- Comment #1 from jamborm at gcc dot gnu dot org 2009-09-07 16:28 ---
We have discussed this in the mailing list thread that eventually lead
to http://gcc.gnu.org/ml/gcc-patches/2009-09/msg00374.html
The bottom line is that we two options:
1) Do not set DECL_VALUE_EXPR to callee copi
