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/51113] [4.7 regression] rev. 181105 causes Firefox profiledbuild failure
Date: Sun, 13 Nov 2011 12:39:00 -0000 [thread overview]
Message-ID: <bug-51113-4-7k5LKBw90K@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51113-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51113
--- Comment #2 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2011-11-13 10:29:54 UTC ---
(In reply to comment #1)
> hm, at a wild guess it looks like -fvisibility-inlines-hidden is not being
> taken into consideration in my patch. If you build without that option, does
> it succeed?
Unfortunately no. I still get the same error as before.
next prev parent reply other threads:[~2011-11-13 10:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 23:36 [Bug gcov-profile/51113] New: " markus at trippelsdorf dot de
2011-11-13 11:31 ` [Bug gcov-profile/51113] " nathan at gcc dot gnu.org
2011-11-13 12:39 ` markus at trippelsdorf dot de [this message]
2011-11-13 14:00 ` markus at trippelsdorf dot de
2011-11-15 8:36 ` markus at trippelsdorf dot de
2011-11-15 9:02 ` markus at trippelsdorf dot de
2011-11-15 9:34 ` markus at trippelsdorf dot de
2011-11-15 10:09 ` markus at trippelsdorf dot de
2011-11-15 20:28 ` nathan at acm dot org
2011-11-15 22:15 ` nathan at gcc dot gnu.org
2011-11-20 10:13 ` nathan at gcc dot gnu.org
2011-12-01 20:00 ` nathan at gcc dot gnu.org
2011-12-05 14:13 ` rguenth at gcc dot gnu.org
2011-12-06 7:23 ` jakub at gcc dot gnu.org
2011-12-06 7:26 ` nathan at gcc dot gnu.org
2011-12-06 8:32 ` jakub at gcc dot gnu.org
2011-12-06 8:53 ` markus at trippelsdorf dot de
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-51113-4-7k5LKBw90K@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).