subject:"\[Bug c\+\+\/59821\] __builtin_LINE and __builtin

[Bug c++/59821] __builtin_LINE and __builtin_FILE for new'd objects is wrong

2014-01-17 Thread rguenth at gcc dot gnu.org

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59821 --- Comment #9 from Richard Biener --- Yeah - sorry for this. As it "worked" for the testcases I tested I was assuming that the locations for the default argument computation (!) stmts should be that of the call, not that of the definition. Appe

[Bug c++/59821] __builtin_LINE and __builtin_FILE for new'd objects is wrong

2014-01-16 Thread jason at gcc dot gnu.org

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59821 Jason Merrill changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/59821] __builtin_LINE and __builtin_FILE for new'd objects is wrong

2014-01-16 Thread jason at gcc dot gnu.org

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59821 --- Comment #7 from Jason Merrill --- Author: jason Date: Thu Jan 16 19:55:12 2014 New Revision: 206686 URL: http://gcc.gnu.org/viewcvs?rev=206686&root=gcc&view=rev Log: PR c++/59821 * tree.c (bot_manip): Update the location of builtin_LI

[Bug c++/59821] __builtin_LINE and __builtin_FILE for new'd objects is wrong

2014-01-16 Thread jason at gcc dot gnu.org

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59821 Jason Merrill changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned at

[Bug c++/59821] __builtin_LINE and __builtin_FILE for new'd objects is wrong

2014-01-16 Thread jason at gcc dot gnu.org

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59821 --- Comment #6 from Jason Merrill --- (In reply to Jakub Jelinek from comment #4) > While I agree with that, for _builtin_{LINE,FILE,FUNCTION} (), those were > added specifically for the use in default arguments and were I think from > the start m

[Bug c++/59821] __builtin_LINE and __builtin_FILE for new'd objects is wrong

2014-01-16 Thread aldyh at gcc dot gnu.org

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59821 --- Comment #5 from Aldy Hernandez --- (In reply to Jason Merrill from comment #3) > I think gimplify_arg clobbering a valid EXPR_LOCATION is wrong; both cases > should give the location of the default argument definition. > > Aldy, what was the

[Bug c++/59821] __builtin_LINE and __builtin_FILE for new'd objects is wrong

2014-01-16 Thread jakub at gcc dot gnu.org

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59821 --- Comment #4 from Jakub Jelinek --- While I agree with that, for _builtin_{LINE,FILE,FUNCTION} (), those were added specifically for the use in default arguments and were I think from the start meant to give you the location of the call, not of