This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug optimization/14863] [3.4 regression] unit-at-a-time causes miscompilation
- From: "rguenth at tat dot physik dot uni-tuebingen dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 7 Apr 2004 12:04:40 -0000
- Subject: [Bug optimization/14863] [3.4 regression] unit-at-a-time causes miscompilation
- References: <20040406114325.14863.rguenth@tat.physik.uni-tuebingen.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From rguenth at tat dot physik dot uni-tuebingen dot de 2004-04-07 12:04 -------
Subject: Re: [3.4 regression] unit-at-a-time causes
miscompilation
On Wed, 7 Apr 2004, 1319 at bot dot ru wrote:
>
> ------- Additional Comments From 1319 at bot dot ru 2004-04-07 11:55 -------
> I have just found that this bug can be triggered on/off using --param
> large-function-insns=<something> option. Default value of this changed from
> 10000 before gcc-3_4-branch creation to 3000 shortly after.
>
> All versions of 3.4.0 and 3.5.0 I tried (20040116..now) are OK with '-O1
> -funit-at-a-time --param large-function-insns=10000' and all failed with '-O1
> -funit-at-a-time --param large-function-insns=3000'.
Yes, it sounds the bug is triggered by (not) inlining some special
function somewhere special. At least I didn't find an optimization
switch, if disabled, that cures the failure at -O1 -funit-at-a-time.
Testcase is still minimizing (slowly).
Richard.
--
Richard Guenther <richard dot guenther at uni-tuebingen dot de>
WWW: http://www.tat.physik.uni-tuebingen.de/~rguenth/
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14863