public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/66319] [6 Regression] gcov-tool.c:84:65: error: invalid conversion from 'int (*)(const c har*, const stat*, int, FTW*)' to 'int (*)(const char*, const stat*, int, FTW)'
Date: Fri, 16 Oct 2015 00:36:00 -0000	[thread overview]
Message-ID: <bug-66319-4-IePc6yRsWM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66319-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66319

--- Comment #10 from dave.anglin at bell dot net ---
On 2015-10-15, at 10:32 AM, josephpattara at gmail dot com wrote:

> Is there a similar fix also for the ia64 platform?

I believe a similar fix could be developed along the lines of the change in
comment #7.  I looked at
the 11.31 defines in developing the PA-RISC change.

It would be very helpful if you could work on this and try to develop a fix for
ia64.  Not many have access
to ia64 systems.

Dave
--
John David Anglin       dave.anglin@bell.net


      parent reply	other threads:[~2015-10-16  0:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 23:58 [Bug gcov-profile/66319] New: " danglin at gcc dot gnu.org
2015-05-28  7:33 ` [Bug gcov-profile/66319] " rguenth at gcc dot gnu.org
2015-05-30 14:21 ` ebotcazou at gcc dot gnu.org
2015-06-02 13:28 ` [Bug bootstrap/66319] " jason at gcc dot gnu.org
2015-06-02 17:51 ` jason at gcc dot gnu.org
2015-06-04 17:43 ` jason at gcc dot gnu.org
2015-06-06 18:33 ` danglin at gcc dot gnu.org
2015-06-06 18:35 ` danglin at gcc dot gnu.org
2015-10-15 14:32 ` josephpattara at gmail dot com
2015-10-16  0:36 ` dave.anglin at bell dot net [this message]

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-66319-4-IePc6yRsWM@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).