This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Fix lost locus issues at -O0 -g (PRs debug/29609, debug/36690, debug/37616)
On Wed, Oct 08, 2008 at 12:49:09PM +0200, Richard Guenther wrote:
> On Wed, Oct 8, 2008 at 12:42 PM, Eric Botcazou <ebotcazou@adacore.com> wrote:
> >> While backporting the patch to 4.3-RH, I've discovered one case where I
> >> haven't handled the goto_locus(location_t)+goto_block -> goto_locus(int
> >> locator) translation, which on the trunk didn't trigger on any of the
> >> testcases, but could, and on 4.3 branch it did.
> >
> > Slightly off topic, but what about backporting the patch to the official 4.3
> > branch as well? The PRs are marked as regressions for it and IMHO they are
> > serious as far as debuggability is concerned. We (AdaCore) are seeing them
> > in our 4.3 compiler so we'll need to do something too. Rather than having
> > each distributor backport the patch internally, why not do it officially?
>
> FYI I think this would be a good idea.
Sure, can we give it a week on the trunk (and in Fedora development repo) before
submitting the backport though?
Jakub
- References:
- [PATCH] Fix lost locus issues at -O0 -g (PRs debug/29609, debug/36690, debug/37616)
- Re: [PATCH] Fix lost locus issues at -O0 -g (PRs debug/29609, debug/36690, debug/37616)
- Re: [PATCH] Fix lost locus issues at -O0 -g (PRs debug/29609, debug/36690, debug/37616)
- Re: [PATCH] Fix lost locus issues at -O0 -g (PRs debug/29609, debug/36690, debug/37616)
- Re: [PATCH] Fix lost locus issues at -O0 -g (PRs debug/29609, debug/36690, debug/37616)