X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=6dw7TBQ5mJXmPw6qB5LXAogbGbbfDvAmS4j9iufLDOw=;
	b=piN30iufDXfD6xwluYKFw4Ta54FWWRKhjUEfy34o0Kwu8FZ7X06xJYea8iI3/pHPRD
	CQFp2BvsDxqQfbRCHNkgV26tHiUXXC5XhgyJcbbcube1KT/6iALaleJSSLj9PGUSMDpE
	rUvbyadQvXl6VMFCsaQlLtLghodj5zYtt6qhXlGFHWbrWWX+uKjNS8QJd6KOuPTPw3V8
	u44Gr60W2ulbxAfaEgqrNQbGAJQobxhJeupDUryMeSOVB6kdFmxupISluYwpraZhM8o3
	IcSleDvW2NRmlfd+7g7DvUX2LztseZ2r6tIPt7u/kG6fnK/Xk2IBwh8ZYsOKBzkMbURr
	M1Jw==
MIME-Version:	1.0
X-Received:	by 10.180.23.231 with SMTP id p7mr18036587wif.30.1444137223455;
	Tue, 06 Oct 2015 06:13:43 -0700 (PDT)
In-Reply-To:	<5613C2EC.7080900@jump-ing.de>
References:	<20151006115833 DOT GA6570 AT visitor2 DOT iram DOT es>
	<5613C2EC DOT 7080900 AT jump-ing DOT de>
Date:	Tue, 6 Oct 2015 18:13:43 +0500
Message-ID:	<CABuVar+GiaN+41KA8=dk88xebt4Hr1Q13v5T9Pya+15JYJgkqg@mail.gmail.com>
Subject:	Re: [geda-user] How to fix gerbv to compile with gcc5?
From:	"Sergey Stepanov (no DOT such DOT process AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

look at this patch:

http://git.geda-project.org/gerbv/commit/?h=home/ssn/build_fix&id=f05d45ac1871115fb3fc03375a47dc2c7f5270c1

2015-10-06 17:47 GMT+05:00 Markus Hitter (mah AT jump-ing DOT de) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com>:
> Am 06.10.2015 um 13:58 schrieb Gabriel Paubert:
>
>> This is a very simple patch, but you
>> don't get the advantages of inlining.
>
> Thanks for the patch, Gabriel. AFAIK functions from other compilation
> units are never inlined, unless a relatively new technology named LTO
> (link time optimisation) enters the picture.
>
> Even then, gcc is quite good at inlining automatically, so using
> 'inline' at all is pretty moot. Exception are function definitions (not
> declarations) in header files, which work with 'inline', only.
>
>
>> Anyaway here is the patch I have rigt now in my tree, disregard the "#if 0"
>> for [...]
>
> Yes, a patch with a bit more love (tidiness) applied would be nice and
> making the patch from a Git commit would also put your credentials into
> the repo. No need to hide your contribution.
>
>
> Markus
>
> --
> - - - - - - - - - - - - - - - - - - -
> Dipl. Ing. (FH) Markus Hitter
> http://www.jump-ing.de/

- Raw text -