[Bug debug/24943] [hppa64] Bad dwarf output using non-preserved base register

2019-03-13 Thread dave.anglin at bell dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24943 --- Comment #11 from dave.anglin at bell dot net --- On 2019-03-13 4:09 a.m., rguenth at gcc dot gnu.org wrote: > So it's a target issue, not a debug one. Of course we could avoid generating > wrong-debug by generating none whenever the argument

[Bug debug/24943] [hppa64] Bad dwarf output using non-preserved base register

2019-03-13 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24943 Richard Biener changed: What|Removed |Added CC||aoliva at gcc dot gnu.org --- Comment

[Bug debug/24943] [hppa64] Bad dwarf output using non-preserved base register

2019-03-12 Thread dave.anglin at bell dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24943 --- Comment #9 from dave.anglin at bell dot net --- The problem is there isn't a fixed relationship between the stack pointer register, %r30, and the argument pointer register, %r29.  HP didn't provide a slot in the stack frame to save the

[Bug debug/24943] [hppa64] Bad dwarf output using non-preserved base register

2012-01-12 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24943 Richard Guenther rguenth at gcc dot gnu.org changed: What|Removed |Added Status|WAITING |NEW ---

[Bug debug/24943] [hppa64] Bad dwarf output using non-preserved base register

2012-01-11 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24943 Richard Guenther rguenth at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |WAITING

[Bug debug/24943] [hppa64] Bad dwarf output using non-preserved base register

2012-01-11 Thread dave.anglin at bell dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24943 --- Comment #7 from dave.anglin at bell dot net 2012-01-11 16:29:48 UTC --- On 1/11/2012 9:54 AM, rguenth at gcc dot gnu.org wrote: Is this still an issue? Yes.

[Bug debug/24943] [hppa64] Bad dwarf output using non-preserved base register

2006-03-19 Thread tausq at debian dot org
--- Comment #5 from tausq at debian dot org 2006-03-20 02:34 --- Indeed, as Dave said this is a different and not yet fixed problem. -- tausq at debian dot org changed: What|Removed |Added

[Bug debug/24943] [hppa64] Bad dwarf output using non-preserved base register

2006-03-18 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-03-18 17:31 --- I thought this was fixed for 4.1.0. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

[Bug debug/24943] [hppa64] Bad dwarf output using non-preserved base register

2006-03-18 Thread dave at hiauly1 dot hia dot nrc dot ca
--- Comment #4 from dave at hiauly1 dot hia dot nrc dot ca 2006-03-18 17:57 --- Subject: Re: [hppa64] Bad dwarf output using non-preserved base register --- Comment #3 from pinskia at gcc dot gnu dot org 2006-03-18 17:31 --- I thought this was fixed for 4.1.0. I don't

[Bug debug/24943] [hppa64] Bad dwarf output using non-preserved base register

2005-12-07 Thread tausq at debian dot org
--- Comment #2 from tausq at debian dot org 2005-12-08 05:26 --- Some discussion about this PR is here: http://gcc.gnu.org/ml/gcc-patches/2005-11/msg01563.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24943

[Bug debug/24943] [hppa64] Bad dwarf output using non-preserved base register

2005-11-19 Thread tausq at debian dot org
--- Comment #1 from tausq at debian dot org 2005-11-20 03:38 --- I forgot to mention that the above was compiled with gcc -g -o dwarfbug dwarfbug.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24943