public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/38753] gcc 4.4.0 20090106 - make profiledbootstrap - No ".gcda" files created in the libiberty/pic directory
Date: Fri, 09 Jan 2009 22:04:00 -0000	[thread overview]
Message-ID: <20090109220430.12793.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38753-13830@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from rob1weld at aol dot com  2009-01-09 22:04 -------
(In reply to comment #8)
> The pic library is not used while compiling gcc so this warning is ok and
> not a bug.
Reopened.

That "bug" would be fixed it the "-fprofile-use" option were not given in
the directories that are expected to be empty of ".gcda" files. We could
get the Makefile's formula to look for ".gcda" files first and compile the
corresponding ".c" files, then compile the remaining ".c" files _without_
using "-fprofile-use" -- not much to figure out and no spurious warnings.


The _other_ bugs are:

2. ... _every_ file in gcc_build/zlib failed to create it's accompanying
  ".gcda" files ... and we miss an opportunity to optimize this library. 

3. There is a "-Werror" to be fixed. Use: "i386.o-warn = -Wno-error"

4. The Makefile won't restart in the correct spot if the build breaks.
  It takes hours to re-configure and re-build what it already has done.

5. The "C" and "Ada" Languages are being profiled (for the most part) but
 the c++,fortran,java,objc,obj-c++ compilers are NOT profiled at all.


Rob


-- 

rob1weld at aol dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38753


  parent reply	other threads:[~2009-01-09 22:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 12:12 [Bug middle-end/38753] New: " rob1weld at aol dot com
2009-01-07 12:28 ` [Bug middle-end/38753] " rob1weld at aol dot com
2009-01-07 13:11 ` rob1weld at aol dot com
2009-01-07 17:34 ` rob1weld at aol dot com
2009-01-07 17:40 ` jakub at gcc dot gnu dot org
2009-01-07 20:58 ` rob1weld at aol dot com
2009-01-07 21:07 ` rob1weld at aol dot com
2009-01-08 17:53 ` rob1weld at aol dot com
2009-01-09 20:30 ` pinskia at gcc dot gnu dot org
2009-01-09 22:04 ` rob1weld at aol dot com [this message]
2009-01-09 22:07 ` pinskia at gcc dot gnu dot org
2009-01-11  4:50 ` rob1weld at aol dot com

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=20090109220430.12793.qmail@sourceware.org \
    --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).