public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: jj@sunsite.ms.mff.cuni.cz, schwab@issan.informatik.uni-dortmund.de
Cc: egcs@cygnus.com
Subject: Re: toplev.c
Date: Mon, 19 Jan 1998 02:06:00 -0000	[thread overview]
Message-ID: <199801182113.QAA01870@caip.rutgers.edu> (raw)

 > From: Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>
 > 
 > Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz> writes:
 > 
 > |> Hi!
 > |> In toplev.c I read:
 > 
 > |> #ifdef __alpha
 > |> extern char *sbrk ();
 > |> #endif
 > 
 > |> Now, this prototype is needed not only for alpha, but for all 64bit
 > |> platforms which have sizeof(void *) > sizeof(int).
 > 
 > Actually every platform would benefit from it, unless there is a conflict
 > with some broken header.
 > -- 
 > Andreas Schwab                                      "And now for something

	You can add GCC_NEED_DECLARATION(sbrk) to configure.in and put
#ifdef NEED_DECLARATION_SBRK wrapper around the extern decl. 

		--Kaveh
--
Kaveh R. Ghazi			Project Manager / Custom Development
ghazi@caip.rutgers.edu		ICon CMT Corp.

             reply	other threads:[~1998-01-19  2:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-19  2:06 Kaveh R. Ghazi [this message]
1998-01-19  9:41 ` toplev.c Richard Henderson
  -- strict thread matches above, loose matches on Subject: below --
1998-01-15 16:30 toplev.c Jakub Jelinek
1998-01-17  1:40 ` toplev.c Andreas Schwab
1998-01-17 22:30 ` toplev.c Jeffrey A Law
1998-01-19  2:25   ` toplev.c Robert Lipe
1998-01-20  2:21     ` toplev.c Klaus Kaempf
1998-01-20  7:07 ` toplev.c Jeffrey A Law

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=199801182113.QAA01870@caip.rutgers.edu \
    --to=ghazi@caip.rutgers.edu \
    --cc=egcs@cygnus.com \
    --cc=jj@sunsite.ms.mff.cuni.cz \
    --cc=schwab@issan.informatik.uni-dortmund.de \
    /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).