public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Mack Lobell" <macklobell@hotmail.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/9185: gcc produces errornous code on cygwin host when -fomit-frame-pointer is used together with -O2 or -O3 Date: Mon, 06 Jan 2003 22:46:00 -0000 [thread overview] Message-ID: <20030106224601.16860.qmail@sources.redhat.com> (raw) The following reply was made to PR c/9185; it has been noted by GNATS. From: "Mack Lobell" <macklobell@hotmail.com> To: dannysmith@users.sourceforge.net, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c/9185: gcc produces errornous code on cygwin host when -fomit-frame-pointer is used together with -O2 or -O3 Date: Mon, 06 Jan 2003 22:34:16 +0000 The fix in PR8750 solves the problem. Verified with gcc3.3 and gcc3.4. //Regards >From: Danny Smith <dannysmith@clear.net.nz> >Reply-To: Danny Smith <dannysmith@users.sourceforge.net> >To: macklobell@hotmail.com, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, >gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org >Subject: Re: c/9185: gcc produces errornous code on cygwin host when >-fomit-frame-pointer is used together with -O2 or -O3 >Date: Mon, 06 Jan 2003 20:51:17 +0000 > > >http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=g >cc&pr=9185 > >I think this may be related to PR8750 and (IMO, erroneously) closed >PR6810. >Could you try the patch to i386.c (ix86_expand_prologue ) that is in the >8750 audit trail. It may not be correct patch but at least it seems to >fix 8750 and *this PR on mingw32 > >Danny _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
next reply other threads:[~2003-01-06 22:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-06 22:46 Mack Lobell [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-07 1:04 bangerth 2003-01-06 21:06 Danny Smith 2003-01-06 13:36 macklobell
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=20030106224601.16860.qmail@sources.redhat.com \ --to=macklobell@hotmail.com \ --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).