This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] Fix PR57451 (Incorrect debug ranges emitted for -freorder-blocks-and-partition -g)
- From: Steve Ellcey <sellcey at mips dot com>
- To: Teresa Johnson <tejohnson at google dot com>
- Cc: Jeff Law <law at redhat dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, Cary Coutant <ccoutant at google dot com>, "Christophe Lyon" <christophe dot lyon at linaro dot org>, <rdsandiford at googlemail dot com>
- Date: Thu, 22 Aug 2013 16:49:50 -0700
- Subject: Re: [PATCH] Fix PR57451 (Incorrect debug ranges emitted for -freorder-blocks-and-partition -g)
- References: <CAAe5K+V2-qGQBbHmNXmzfDePk96xni5tgUMw2G0fRKa8EE01pA at mail dot gmail dot com>
On Mon, 2013-08-19 at 22:21 -0700, Teresa Johnson wrote:
> 2013-08-19 Teresa Johnson <email@example.com>
> PR rtl-optimizations/57451
> * final.c (reemit_insn_block_notes): Prevent lexical blocks
> from crossing split section boundaries.
> * testsuite/g++.dg/tree-prof/pr57451.C: New test.
This patch is causing a problem in my mips compiler. I am creating a
cross-toolchain running on x86 targeting mips-mti-linux-gnu and if I
compile glibc using a GCC that has this patch all of the programs I
compile go into an infinite loop when run under the qemu simulator. I
think it is the dynamic linker that is getting miscompiled, but I
haven't tracked down the exact nature of the miscompilation yet. Has
anyone else reported any problems with it? I am adding Richard
Sandiford to the email list since he is a mips expert and also might
have some insight to using next_active_insn vs. next_real_insn vs.
next_insn, though it doesn't look like you have changed what is used