public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "micis at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/15760] Loop unrolling bug with max-unrolled-insns=200 Date: Tue, 01 Jun 2004 10:28:00 -0000 [thread overview] Message-ID: <20040601102824.16351.qmail@sourceware.org> (raw) In-Reply-To: <20040601102239.15760.micis@gmx.de> ------- Additional Comments From micis at gmx dot de 2004-06-01 10:28 ------- This bug is present in gcc for a long time, at least in gcc 3.3.3 I only issue it here again, because it was stated, that it had been fixed in the 2nd prerelease of gcc3.3.4 output from gcc -v Reading specs from /usr/local/gcc33/lib/gcc-lib/powerpc-unknown-linux- gnu/3.3.4/specs Configured with: ../gcc33/configure --prefix=/usr/local/gcc33 --program- suffix=33 --with-cpu=7450 --enable-altivec --enable-languages=c,c++ --with- fmessage-length=0 --with-falign-loops=16 --with-falign-jumps=16 --with-falign- functions=32 --with-fstrict-aliasing --with-funroll-loops --with-mpowerpc- gpopt --with-fsched-interblock --with-fno-gcse-sm : (reconfigured) ../gcc33/configure --prefix=/usr/local/gcc33 --program- suffix=33 --with-cpu=7450 --enable-altivec --enable-languages=c,c++ Thread model: posix gcc version 3.3.4 20040530 (prerelease) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15760
next prev parent reply other threads:[~2004-06-01 10:28 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-06-01 10:22 [Bug middle-end/15760] New: " micis at gmx dot de 2004-06-01 10:28 ` micis at gmx dot de [this message] 2004-06-01 11:26 ` [Bug middle-end/15760] " pinskia at gcc dot gnu dot org 2004-06-01 14:20 ` bangerth at dealii dot org 2004-08-14 7:19 ` pinskia at gcc dot gnu dot org
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=20040601102824.16351.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).