public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/50647] gcc/system.h: wrong prototype for sbrk
Date: Fri, 07 Oct 2011 21:50:00 -0000	[thread overview]
Message-ID: <bug-50647-4-b8iAZJqkbb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50647-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-10-07 21:49:58 UTC ---
In general the declarations in system.h are expected to be used only for 
very archaic hosts that do not have prototypes in their system headers.  
For such hosts, int is probably the right argument type; this prototype 
should never be used for modern hosts.  As such, the prototype should 
probably remain unchanged; no host that actually has intptr_t should ever 
see it.  The problem would be that the declaration was not detected; we 
need more details of the host (including whether you were e.g. building 
natively or building a Canadian cross).

AC_USE_SYSTEM_EXTENSIONS should already ensure all appropriate feature 
test macros are defined for known hosts.


  parent reply	other threads:[~2011-10-07 21:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07  2:02 [Bug c/50647] New: " fzvqedi at v dot mintemail.com
2011-10-07  5:52 ` [Bug other/50647] " pinskia at gcc dot gnu.org
2011-10-07 20:57 ` fzvqedi at v dot mintemail.com
2011-10-07 21:50 ` joseph at codesourcery dot com [this message]
2011-10-07 21:54 ` joseph at codesourcery dot com
2011-10-07 22:30 ` schwab@linux-m68k.org
2011-10-09 23:30 ` fzvqedi at v dot mintemail.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=bug-50647-4-b8iAZJqkbb@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).