This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: target/3920: [PPC] wrong register number for CTR in stabs
- From: "Mattias Engdegård" <mattias at virtutech dot se>
- To: geoffk at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 13 Jan 2003 10:06:02 -0000
- Subject: Re: target/3920: [PPC] wrong register number for CTR in stabs
- Reply-to: "Mattias Engdegård" <mattias at virtutech dot se>
The following reply was made to PR target/3920; it has been noted by GNATS.
From: "=?ISO-8859-1?Q?Mattias Engdeg=E5rd?=" <mattias@virtutech.se>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
geoffk@gcc.gnu.org, mattias@virtutech.se, gcc-gnats@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, geoffk@gcc.gnu.org
Subject: Re: target/3920: [PPC] wrong register number for CTR in stabs
Date: Mon, 13 Jan 2003 10:56:12 +0100
Gcc 3.2.1 behaves identically to 3.0.1 in this respect:
I cannot get gcc to emit Stabs/DWARF info saying that a variable lives
in CTR, so even if gcc has the wrong number for it, this has no ill
effect. Even if a variable lives in CTR inside a loop, the Stabs/DWARF
will have it in some general integer register instead.
The latter is a quality-of-debug-info bug.