public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: <martin@bruli.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/8873: Optimization on alpha (ev5) Date: Fri, 07 Mar 2003 09:36:00 -0000 [thread overview] Message-ID: <20030307093601.1868.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/8873; it has been noted by GNATS. From: <martin@bruli.net> To: <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: optimization/8873: Optimization on alpha (ev5) Date: Fri, 7 Mar 2003 10:30:18 +0100 > The last gcc version you can compile and run all off > - linux-2.4 > - glibc-2.2.5 > - modutils-2.4 > is 2.95.3. All later version will generate invalid (not runnable > code) on my alphas. And I have tested _all_ versions after 2.95.3. > No I went back to 2.95.3 with the disadvantage that the most > recent glibc version that can be compiled is 2.2.5. Which versions did you try? All. - 3.0.1 - 3.0.2 - 3.0.3 - 3.0.4 - 3.1 - 3.1.1 - 3.2 - 3.2.1 This took me about one year! Because after compile and install of the compile I rebuilt or at least I tried to rebuild all of 1. binutils 2. gcc again, with the new binutils from step 1 3. linux kernel 4. modutils 5. glibc-2.2.5 After the rebuild of all this I run the new installation and tested out some applications including - apache - mysql - squid - ssh - wu-ftpd - openssl - ISC bind - gdb The test consisted of compile/build, install and run some test scripts comparing the results to the correct results generated on a gcc-2.95.3 based installation. When ever I found fatal errors I went to the next gcc version starting at the beginning of the build process but it got worse from version to version. At the end I gave up and reinstalled the system totally based on gcc-2.95.3. - That's the story. Regards, -- Martin
next reply other threads:[~2003-03-07 9:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-07 9:36 martin [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-19 9:06 Eric Botcazou 2003-02-18 17:16 martin 2003-02-18 13:40 ebotcazou 2002-12-08 15:46 Falk Hueffner 2002-12-08 7:16 martin
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=20030307093601.1868.qmail@sources.redhat.com \ --to=martin@bruli.net \ --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).