http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #17 from Jakub Jelinek 2013-01-28
14:33:18 UTC ---
Should be fixed now on the trunk, but keeping the PR open, so that we don't
forget to revert and do a better fix instead.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #16 from Jakub Jelinek 2013-01-28
14:05:48 UTC ---
Author: jakub
Date: Mon Jan 28 14:05:40 2013
New Revision: 195504
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=195504
Log:
PR tree-optimization/56094
* g
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #15 from Richard Biener 2013-01-28
08:55:55 UTC ---
(In reply to comment #12)
> Created attachment 29272 [details]
> gcc48-pr56094.patch
>
> input_location is used heavily in the gimplifier, gimplify_expr sets it from
> the
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #14 from Jakub Jelinek 2013-01-25
12:04:59 UTC ---
(In reply to comment #13)
> You are explaining how it works right now. What I am asking is how we want it
> to work, that is, why the gimplifier needs to care about input_location a
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #13 from Manuel López-Ibáñez 2013-01-25
11:43:37 UTC ---
(In reply to comment #12)
> Created attachment 29272 [details]
> gcc48-pr56094.patch
>
> input_location is used heavily in the gimplifier, gimplify_expr sets it from
> the exp
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #12 from Jakub Jelinek 2013-01-25
11:29:13 UTC ---
Created attachment 29272
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29272
gcc48-pr56094.patch
input_location is used heavily in the gimplifier, gimplify_expr sets i
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #11 from Manuel López-Ibáñez 2013-01-24
20:49:33 UTC ---
(In reply to comment #10)
>
> Input_location should only be used from parsing. Other places reuse the
> variable and those happen to eventually pick up stale values, such as
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #10 from rguenther at suse dot de
2013-01-24 19:30:54 UTC ---
"manu at gcc dot gnu.org" wrote:
>
>http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
>
>--- Comment #9 from Manuel López-Ibáñez
>2013-01-24 18:39:18 UTC ---
>> During
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #9 from Manuel López-Ibáñez 2013-01-24
18:39:18 UTC ---
> During original gimplification, I can understand the OR_HERE (aka
> input_location) part there, or in passes that maintain input_location.
I thought gimplification happens af
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #8 from rguenther at suse dot de
2013-01-24 18:37:30 UTC ---
"jakub at gcc dot gnu.org" wrote:
>
>http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
>
>--- Comment #6 from Jakub Jelinek 2013-01-24
>17:26:48 UTC ---
>---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
--- Commen
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #6 from Jakub Jelinek 2013-01-24
17:26:48 UTC ---
--- gimplify.c.jj2013-01-11 09:02:55.0 +0100
+++ gimplify.c2013-01-24 18:15:54.246157569 +0100
@@ -8600,6 +8600,7 @@ force_gimple_operand_1 (tree expr, gimpl
{
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #5 from Jakub Jelinek 2013-01-24
15:06:28 UTC ---
So, the reason seems to be:
mod = build2 (INIT_EXPR, TREE_TYPE (t), t, unshare_expr (val));
SET_EXPR_LOCATION (mod, EXPR_LOC_OR_HERE (val));
in:
#0 internal_get
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #4 from Jakub Jelinek 2013-01-24
14:19:17 UTC ---
On a brief look, this doesn't look like using location of neighbouring
statement, given:
grep 66:1 pr56094.c.115t.cunroll | wc -l
0
grep 66:1 pr56094.c.119t.ivopts | wc -l
39
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
Richard Biener changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #2 from Joshua Conner 2013-01-24
04:05:09 UTC ---
Sorry, I should have been more specific -- the function I'm describing in the
previous comments is "test_main".
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094
--- Comment #1 from Joshua Conner 2013-01-24
04:03:44 UTC ---
Created attachment 29263
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29263
Reduced test case
17 matches
Mail list logo
