public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ebotcazou@gcc.gnu.org To: enrio@online.no, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: optimization/10752: -O2 generates loop assembly instruction with label too far away Date: Wed, 14 May 2003 13:56:00 -0000 [thread overview] Message-ID: <20030514135602.12419.qmail@sources.redhat.com> (raw) Synopsis: -O2 generates loop assembly instruction with label too far away State-Changed-From-To: feedback->closed State-Changed-By: ebotcazou State-Changed-When: Wed May 14 13:56:02 2003 State-Changed-Why: Duplicate of PR optimization/9888. Fixed in GCC 3.2.3 and later. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10752
next reply other threads:[~2003-05-14 13:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-14 13:56 ebotcazou [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-14 19:16 Enrique Perez-Terron 2003-05-14 10:48 giovannibajo 2003-05-12 17:16 Dara Hazeghi 2003-05-12 15:26 enrio
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=20030514135602.12419.qmail@sources.redhat.com \ --to=ebotcazou@gcc.gnu.org \ --cc=enrio@online.no \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.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).