public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: nirkko@dkf6.unibe.ch To: gcc-gnats@gcc.gnu.org Subject: optimization/6193: -funroll-loops leads to bootstrap failure in gcc-3.0.4 Date: Fri, 05 Apr 2002 13:26:00 -0000 [thread overview] Message-ID: <20020405212534.25683.qmail@sources.redhat.com> (raw) >Number: 6193 >Category: optimization >Synopsis: -funroll-loops leads to bootstrap failure in gcc-3.0.4 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Apr 05 13:26:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: nirkko >Release: gcc version 3.0.4 >Organization: >Environment: Sun SPARC Solaris 2.6 >Description: bootstrap of gcc-3.0.4 fails with -funroll-loops. other optimizations including -O3 are alright. (gcc-3.0.1 bootstrap worked also with -funroll-loops, as far as I remember...) The failure is a stage 2/3 comparison failure for 8 files, as indicated on the output log below. using the script below, the following setting works: set _CFLAGS = "-fPIC -O3 -msupersparc" and the following setting doesn't: set _CFLAGS = "-fPIC -O3 -funroll-loops -msupersparc" configuration/make used: ../$DIRSRC_BUILD/configure \ --prefix=${DIR_PREFIX} --disable-shared \ --with-gnu-as --with-as=/usr/local/bin/as \ --with-gnu-ld --with-ld=/usr/local/bin/ld \ --enable-threads \ --with-cpu=supersparc --enable-cpp \ --enable-version-specific-runtime-libs \ --disable-nls |& /bin/tee $FILE_OUTPUTLOG \ && gmake CONFIG_SHELL=/bin/ksh \ BOOT_CFLAGS="$_CFLAGS" \ CFLAGS="$_CFLAGS" \ LIBCFLAGS="$_CFLAGS" \ LIBCXXFLAGS="$_CFLAGS -no-implicit-templates" \ bootstrap |& /bin/tee -a $FILE_OUTPUTLOG output generated (last lines): ... ... ... if [ -f .bad_compare ]; then \ echo "Bootstrap comparison failure!"; \ cat .bad_compare; \ exit 1; \ else \ case "compare" in \ *-lean ) rm -rf stage$stage ;; \ *) ;; \ esac; true; \ fi Bootstrap comparison failure! crtbegin.o differs gcov.o differs ggc-common.o differs global.o differs gmon.o differs local-alloc.o differs profile.o differs toplev.o differs gmake[1]: *** [compare] Error 1 gmake[1]: Leaving directory `/_mnt/hd2/package/gcc/gcc-3.0.4-static-bimbo2.6-obj/gcc' gmake: *** [bootstrap] Error 2 >How-To-Repeat: bootstrap with -funroll-loops (preprocessed input of these files are identical for stage 2 and 3, but assembly output differs for the stage 2 and 3 compilations. the difference is mainly in temporary labels, but also has other strange differences) >Fix: workaround: bootstrap without -funroll-loops however, will other programs compiled with -funroll-loops be erroneous? this bug report replaces #5888 (where I didn't identify the -funroll-loops as the source of the problem yet). >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="none (bootstrap failure, needs whole gcc-3.0.4 build)" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="none (bootstrap failure, needs whole gcc-3.0.4 build)"
reply other threads:[~2002-04-05 21:26 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020405212534.25683.qmail@sources.redhat.com \ --to=nirkko@dkf6.unibe.ch \ --cc=gcc-gnats@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).