public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Enrique Perez-Terron <enrio@online.no> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/10752: -O2 generates loop assembly instruction with label too far away Date: Wed, 14 May 2003 19:16:00 -0000 [thread overview] Message-ID: <20030514191601.21005.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/10752; it has been noted by GNATS. From: Enrique Perez-Terron <enrio@online.no> To: Dara Hazeghi <dhazeghi@yahoo.com> Cc: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: optimization/10752: -O2 generates loop assembly instruction with label too far away Date: 14 May 2003 21:10:53 +0200 On Mon, 2003-05-12 at 19:11, Dara Hazeghi wrote: > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- > trail&database=gcc&pr=10752 > > Hello, > > I cannot reproduce this problem on gcc 3.2, 3.3 branch (20030510) or > mainline (20030510). Please note that gcc version 3.2.2 20030222 (Red > Hat Linux 3.2.2-5) is not an officially released version. Can you > please try the code in question with 3.2.3 or 3.3 prerelease, and > report whether this problem still occurs? Thanks, > > Dara You are right. I downloaded gcc-3.2.3, and did: $ ./configure --prefix=/home/enrique/root/usr $ make bootstrap $ export PATH=/home/enrique/root/usr/bin:$PATH $ FLAGS="... pasted in from the mail I sent to you ..." $ gcc $FLAGS -c skgepnmi.i and got no error messages. Just to be sure I was testing properly, I reverted PATH to the original, and repeated the compile $ export PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin $ gcc $FLAGS -c skgepnmi.i and got the error messages as described. It seems like I have to send a bug report to Red Hat. Thanks, Enrique
next reply other threads:[~2003-05-14 19:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-14 19:16 Enrique Perez-Terron [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-14 13:56 ebotcazou 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=20030514191601.21005.qmail@sources.redhat.com \ --to=enrio@online.no \ --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).