public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> To: ro@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/5505: Doubts about a patch for OSF Date: Mon, 04 Feb 2002 11:06:00 -0000 [thread overview] Message-ID: <20020204190618.4243.qmail@sources.redhat.com> (raw) The following reply was made to PR target/5505; it has been noted by GNATS. From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> To: Richard.Kreckel@Uni-Mainz.DE Cc: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: target/5505: Doubts about a patch for OSF Date: Mon, 4 Feb 2002 16:56:37 +0100 (MET) Richard B. Kreckel writes: [Please keep gcc-gnats on the Cc: so the whole thread gets archived in GNATS as well. Thanks.] > Hmm, `as' is also from OSFCMPLRS510. But `ld' is more and more becoming a > suspect: mine are from OSFBASE510 (i.e. no patch) and from > OSFPAT00007200510 (i.e. an older patch), respectively. Maybe I can get > hold of OSFPAT00035800510 patch and see if it solves the problems. Not > sure, though, when this can happen... I'll keep you informed. Fine. Instead of patching the whole machine, it should be sufficient to just drop a copy of the patched ld in $prefix/lib/gcc-lib/alpha-dec-osf5.1/3.0.4/ld. > > As I said, make and make check both passed with the above snapshot. I can > > try a fresh bootstrap from current 3.0 branch sources, just to make sure, > > but this may take some time. > > Maybe that would be helpful, just to make sure. As I said: I can revert > your patch from either GCC 3.0.{1,2,3} and it works. The point being > other interferences are not very likely... I've re-bootstrapped GCC 3.0.4 20020129 with no regressions compared to 3.0.2 20010921, and this version still creates a working CLN 1.1.4 which passes make check. I've even tried to drop the Tru64 UNIX V5.1 ld (before any patches) into the gcc tree as mentioned above and rebuilt CLN, which keeps working. This may mean that ld isn't the culprit or the error only happens when linking libstdc++. Rainer
next reply other threads:[~2002-02-04 19:06 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-04 11:06 Rainer Orth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-10 5:36 Rainer Orth 2002-05-10 5:27 ro 2002-05-09 10:56 Richard B. Kreckel 2002-04-16 10:56 Rainer Orth 2002-02-25 8:58 Rainer Orth 2002-02-23 14:12 Richard B. Kreckel 2002-02-22 15:46 Rainer Orth 2002-02-22 14:16 Rainer Orth 2002-02-21 16:21 Richard B. Kreckel 2002-02-20 9:36 Richard B. Kreckel 2002-02-19 5:26 Rainer Orth 2002-02-18 12:56 Richard B. Kreckel 2002-02-04 11:06 Richard B. Kreckel 2002-01-30 6:14 ro 2002-01-27 6:26 kreckel
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=20020204190618.4243.qmail@sources.redhat.com \ --to=ro@techfak.uni-bielefeld.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=ro@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).