X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: bnu214s compiled for djgpp 2.04 alpha
Date: 22 Sep 2004 14:50:43 GMT
Lines: 28
Message-ID: <2rdhq3F191i81U1@uni-berlin.de>
References: <1095849299 DOT 415155532ce78 AT webmail DOT wilkes DOT edu> <41518C5C DOT 1000306 AT acm DOT org>
X-Trace: news.uni-berlin.de q1x5zh4ODVZjOvqcegCdxgweWPxffOt8ZubtVAWvZBWUfy8E8ha691YW3p
X-Orig-Path: not-for-mail
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Cesar Rabak <crabak AT acm DOT org> wrote:
> fdonahoe AT wilkes DOT edu escreveu:
[...]
> > # 628 "./gmp-impl.h"
> > void __gmpz_aorsmul_1 (mp_size_t sub,mpz_ptr w,mpz_srcptr u,mp_limb_t
> > v) __attribute__ ((regparm (1)));
[...]
> > # 60 "mpz/aorsmul_i.c"
> > void
> > __gmpz_aorsmul_1 (mp_size_t sub,mpz_ptr w,mpz_srcptr x,mp_limb_t y)
> > {

> They don't look to have any clash between declaration and definition for 
> me. 

Absence vs. presence of __attribute__((regparm(1)) should not be a
clash?  I would rather strongly expect it to count as one --- if the
__attribute___ is useful at all, it's a change of ABI, which makes the
prototype incompatible with the definition.

BTW: what exaxctly made the GMP people believe they can violate the
ANSI/ISO standard C reserved-for-implementation namespace like that?
This actually means that strictly speaking, the above causes undefined
behaviour, and everything goes.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.