public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/52150] [4.7 regression] junk at end of line in Firefox PGO build
Date: Wed, 08 Feb 2012 10:31:00 -0000 [thread overview]
Message-ID: <bug-52150-4-OeSBTPVamE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52150-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52150
--- Comment #5 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2012-02-08 10:31:27 UTC ---
(In reply to comment #4)
> Created attachment 26607 [details]
> gcc47-pr52150.patch
>
> Untested fix. I took the liberty to also overwrite the last _ with . or $,
> so that at least when possible these artificial symbols don't clash with user
> __gcov__foo etc. symbols (yeah, I know, they are reserved for implementation,
> still the assembly would likely fail if those were used).
The patch fixes the issue and survived a full Firefox PGO build.
Thanks Jakub.
next prev parent reply other threads:[~2012-02-08 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 17:27 [Bug gcov-profile/52150] New: " markus at trippelsdorf dot de
2012-02-07 17:41 ` [Bug gcov-profile/52150] " pinskia at gcc dot gnu.org
2012-02-07 17:43 ` pinskia at gcc dot gnu.org
2012-02-08 0:01 ` jakub at gcc dot gnu.org
2012-02-08 8:04 ` jakub at gcc dot gnu.org
2012-02-08 8:38 ` jakub at gcc dot gnu.org
2012-02-08 10:31 ` markus at trippelsdorf dot de [this message]
2012-02-08 13:27 ` jakub at gcc dot gnu.org
2012-02-08 13:39 ` jakub at gcc dot gnu.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=bug-52150-4-OeSBTPVamE@http.gcc.gnu.org/bugzilla/ \
--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: link
Be 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).