[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-10-23 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 Tom de Vries changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-10-23 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 --- Comment #17 from Tom de Vries --- Author: vries Date: Tue Oct 23 17:16:55 2018 New Revision: 265431 URL: https://gcc.gnu.org/viewcvs?rev=265431=gcc=rev Log: backport "[c++] Fix DECL_BY_REFERENCE of clone parms" Consider test.C compiled at

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-10-23 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 --- Comment #16 from Tom de Vries --- Author: vries Date: Tue Oct 23 15:06:17 2018 New Revision: 265427 URL: https://gcc.gnu.org/viewcvs?rev=265427=gcc=rev Log: backport "[c++] Fix DECL_BY_REFERENCE of clone parms" Consider test.C compiled at

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-10-23 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 --- Comment #15 from Tom de Vries --- Author: vries Date: Tue Oct 23 15:01:12 2018 New Revision: 265426 URL: https://gcc.gnu.org/viewcvs?rev=265426=gcc=rev Log: backport "[c++] Fix DECL_BY_REFERENCE of clone parms" Consider test.C compiled at

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-10-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 Jonathan Wakely changed: What|Removed |Added CC||anton at swarmer dot me --- Comment

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-08-01 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 --- Comment #13 from Tom de Vries --- (In reply to Nikolay Piskun from comment #12) > Great work, thanks. Will this fix propagate to other branches? Patch was OK-ed for "trunk and also for branches after a while".

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-08-01 Thread nikolay.piskun at roguewave dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 --- Comment #12 from Nikolay Piskun --- Great work, thanks. Will this fix propagate to other branches?

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-08-01 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 Richard Biener changed: What|Removed |Added Known to work||9.0 --- Comment #11 from Richard

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-07-31 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 --- Comment #10 from Tom de Vries --- Author: vries Date: Tue Jul 31 15:37:11 2018 New Revision: 263164 URL: https://gcc.gnu.org/viewcvs?rev=263164=gcc=rev Log: [c++] Fix DECL_BY_REFERENCE of clone parms Consider test.C compiled at -O0 -g: ...

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-07-30 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 Tom de Vries changed: What|Removed |Added Keywords||patch --- Comment #9 from Tom de Vries

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-07-30 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 --- Comment #8 from Tom de Vries --- Created attachment 44464 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44464=edit Tentative patch

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-07-30 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 --- Comment #7 from Richard Biener --- (In reply to Tom de Vries from comment #5) > The foo::foo function starts at label .LFB1520, which brings us to: > ... > .uleb128 0x8b # (DIE (0x5a99) DW_TAG_subprogram) > .long 0x5a75

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-07-29 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 --- Comment #6 from Tom de Vries --- Not sure yet whether this is the desired fix, but using this patch: ... diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c index bd45e0b0685..fbbbe9f2d2a 100644

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-07-27 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 --- Comment #5 from Tom de Vries --- The foo::foo function starts at label .LFB1520, which brings us to: ... .uleb128 0x8b # (DIE (0x5a99) DW_TAG_subprogram) .long 0x5a75 # DW_AT_abstract_origin .long .LASF897

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-07-27 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 --- Comment #4 from Tom de Vries --- Reproduced with trunk gcc/gdb: ... $ cat bla.C #include #include using std::string; class foo { public: foo (std::string dir_hint) { std::cout << dir_hint << "\n"; } }; int main (void) {

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-07-27 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 Richard Biener changed: What|Removed |Added Keywords||wrong-debug Target|

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-07-26 Thread nikolay.piskun at roguewave dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 --- Comment #2 from Nikolay Piskun --- How to reproduce; Set a breakpoint on line 48 Look at two variable: base (passed as reference) and dir_hint (passed as copy). They should be the same values, but second one is wrong. Looks like compiler

[Bug debug/86687] Wrong debug information for string types passed as parameters

2018-07-26 Thread nikolay.piskun at roguewave dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687 --- Comment #1 from Nikolay Piskun --- Created attachment 8 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=8=edit Test program How to reproduce; Set a breakpoint on line 48 Look at two variable: base (passed as reference) and