public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au> To: amodra@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/9681: powerpc64 -frepo fails to instantiate some templates Date: Tue, 25 Feb 2003 11:06:00 -0000 [thread overview] Message-ID: <20030225110600.10044.qmail@sources.redhat.com> (raw) The following reply was made to PR target/9681; it has been noted by GNATS. From: Alan Modra <amodra@bigpond.net.au> To: gcc-patches@gcc.gnu.org Cc: gcc-gnats@gcc.gnu.org, janis187@us.ibm.com Subject: Re: target/9681: powerpc64 -frepo fails to instantiate some templates Date: Tue, 25 Feb 2003 21:31:20 +1030 This hack cures the powerpc64-linux -frepo failures. It should be safe enough to always drop a leading '.' rather than making this target-dependent, I think, but if this makes people nervous I'll introduce another #ifdef. * tlink.c (scan_linker_output): Drop leading '.' from symbol names. OK for mainline and 3.3? diff -urpN -xCVS -x'*~' gcc-ppc64-33.orig/gcc/tlink.c gcc-ppc64-33/gcc/tlink.c --- gcc-ppc64-33.orig/gcc/tlink.c 2003-01-12 08:18:20.000000000 +1030 +++ gcc-ppc64-33/gcc/tlink.c 2003-02-25 21:05:20.000000000 +1030 @@ -634,7 +634,13 @@ scan_linker_output (fname) /* Don't let the strstr's below see the demangled name; we might get spurious matches. */ if (p) - p[-1] = '\0'; + { + p[-1] = '\0'; + + /* powerpc64-linux references .foo when calling function foo. */ + if (*p == '.') + p++; + } /* We need to check for certain error keywords here, or we would mistakenly use GNU ld's "In function `foo':" message. */ -- Alan Modra IBM OzLabs - Linux Technology Centre
next reply other threads:[~2003-02-25 11:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-25 11:06 Alan Modra [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-26 4:56 Jim Wilson 2003-02-19 16:15 target/9681: [powerpc64] " dje 2003-02-12 23:46 target/9681: powerpc64 " janis187
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=20030225110600.10044.qmail@sources.redhat.com \ --to=amodra@bigpond.net.au \ --cc=amodra@gcc.gnu.org \ --cc=gcc-prs@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).