public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: caf@guarana.org To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/8988: gcc3.2 and 3.2.1 with -O2 and -mcpu=i386 generates code that segfaults Date: Wed, 18 Dec 2002 05:46:00 -0000 [thread overview] Message-ID: <20021218134607.26918.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/8988; it has been noted by GNATS. From: caf@guarana.org To: paolo@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, kevin@sylandro.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: optimization/8988: gcc3.2 and 3.2.1 with -O2 and -mcpu=i386 generates code that segfaults Date: Thu, 19 Dec 2002 00:37:16 +1100 On Wed, Dec 18, 2002 at 12:54:39PM -0000, paolo@gcc.gnu.org wrote: > Synopsis: gcc3.2 and 3.2.1 with -O2 and -mcpu=i386 generates code that segfaults > > State-Changed-From-To: open->feedback > State-Changed-By: paolo > State-Changed-When: Wed Dec 18 04:54:38 2002 > State-Changed-Why: > For some reason, the attachment got lost. Could you possibly > provide it again? > Thanks, Paolo. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8988 Preprocessed output attached. By the way, the bad assembly that causes the crash is: .L8: leal 1(%ecx), %edx xorl %ecx, %ecx ; %ecx is 0 .p2align 2,,3 .L7: movl %edx, %eax movl %edx, -28(%ebp) leal 2(%ecx), %edx ; %edx is 2 movl %eax, %ecx movb -1(%edx), %al ; we try to read from 0x00000001 - Kevin.
next reply other threads:[~2002-12-18 13:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-18 5:46 caf [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-18 5:46 caf 2002-12-18 4:54 paolo 2002-12-18 4:36 kevin
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=20021218134607.26918.qmail@sources.redhat.com \ --to=caf@guarana.org \ --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).