public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Ellcey <sje@cup.hp.com>
To: bkorb@veritas.com
Cc: gcc@gcc.gnu.org
Subject: Re: HPUX 11 "size_t" fixinc problems
Date: Mon, 03 Dec 2001 16:57:00 -0000	[thread overview]
Message-ID: <200112040057.QAA17664@hpsje.cup.hp.com> (raw)

I wonder if it would be a good idea to also add "STMP_FIXPROTO=" to t-pa
and t-pa64 on the mainline.  At least on HP-UX 11.* I have found no
need to run fixproto as all the headers have the proper prototypes but
fixproto still does some unneccessary fixes when it finds functions with
wrong/obsolete prototypes that are under ifdefs that ensure they will
never be seen by GCC anyway.

This is working fine for me on HP-UX 11.* systems and reduces the number
of headers that get modified, I have not tried it on 10.*.

Steve Ellcey
sje@cup.hp.com

> Therefore, it is my intention to remove all the empty replacement
> non-fixes and wait to see what problems arise.  (I don't have 
> enough of a variety of systems to do it any other way.)  So, I
> have also posted this to the GCC list.
> 
> SO EVERYONE BE ADVISED:  I am removing the protection many headers
> used to have against mis-fixes from fixincludes.  I will put them
> back only if the fixincl program cannot be fixed itself.
> 
> Um, just to be clear:  mainline only, not 3.0 branch.
> 
> Cheers,
> 	Bruce

             reply	other threads:[~2001-12-04  0:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 16:57 Steve Ellcey [this message]
     [not found] <200112011947.fB1JlOgI006616@hiauly1.hia.nrc.ca>
2001-12-03 10:37 ` Bruce Korb
2001-12-17 12:36   ` John David Anglin

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=200112040057.QAA17664@hpsje.cup.hp.com \
    --to=sje@cup.hp.com \
    --cc=bkorb@veritas.com \
    --cc=gcc@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).