public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Juergen Keil <jk@tools.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/3480: gcc-3.0, bad code generated with -O3 -fomit-frame-pointer on intel x86 Date: Mon, 03 Dec 2001 04:36:00 -0000 [thread overview] Message-ID: <20011203123603.12027.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/3480; it has been noted by GNATS. From: Juergen Keil <jk@tools.de> To: chr.breitkopf@magrathea.de, rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, jk@tools.de, nobody@gcc.gnu.org Cc: Subject: Re: optimization/3480: gcc-3.0, bad code generated with -O3 -fomit-frame-pointer on intel x86 Date: Mon, 3 Dec 2001 13:30:00 +0100 (MET) > Synopsis: gcc-3.0, bad code generated with -O3 -fomit-frame-pointer on in= tel=20 x86 >=20 > State-Changed-From-To: open->feedback > State-Changed-By: rodrigc > State-Changed-When: Sat Dec 1 22:49:12 2001 > State-Changed-Why: > I think this has been fixed by: > http://gcc.gnu.org/ml/gcc-patches/2001-11/msg00698.html > =20 > Can you try a gcc 3.0.3 snapshot and verify this? >=20 >=20 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&pr=3D3480&d= atabase=3Dg cc Yes, the problem seems to be fixed. I've downloaded and installed snapshot gcc-20011126 and the code generated for the problematic function 'acmStreamOpen' looks much better now: .type acmStreamOpen,@function acmStreamOpen: pushl %ebp pushl %edi pushl %esi pushl %ebx subl $16, %esp movl 44(%esp), %esi <-- third parameter is now accessed via %es= p=20 with correct offset movzwl 16(%esi), %ecx movl 48(%esp), %ebx In the released versions of gcc-3.0.x, the following buggy code is generate= d (from my bug report) =09.globl acmStreamOpen =09.type acmStreamOpen,@function =09acmStreamOpen: =09pushl %ebp =09pushl %edi =09pushl %esi =09pushl %ebx =09subl $96, %esp =09movl 12(%ebp), %esi <--- accesses pwfxSrc as offset(%ebp), no =09=09=09 <--- valid %ebp setup yet! =09movzwl 16(%esi), %edx =09movl 16(%ebp), %ebx -- J=FCrgen Keil =09=09jk@tools.de Tools GmbH=09=09=09+49 (228) 9858011
next reply other threads:[~2001-12-03 12:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-03 4:36 Juergen Keil [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-12-11 22:26 rodrigc 2001-12-11 22:22 rodrigc 2001-12-03 4:36 Juergen Keil 2001-12-03 4:06 Christoph Breitkopf 2001-12-01 22:56 rodrigc 2001-12-01 22:49 rodrigc
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20011203123603.12027.qmail@sources.redhat.com \ --to=jk@tools.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).