Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis results for 2018-10-09
Date: Thu, 11 Oct 2018 10:39:15 +0200	[thread overview]
Message-ID: <20181011103915.69e80d88@windsurf> (raw)
In-Reply-To: <87y3b5ks97.fsf@tkos.co.il>

Hello,

On Thu, 11 Oct 2018 07:43:32 +0300, Baruch Siach wrote:

> The build only fails with the CT-NG PowerPC e500 toolchain. Is that the
> only gcc 4.7 toolchain?
> 
> This is the failing code:
> 
> typedef double hbase_f(double);
> 
> class StatHist
> {
>     ...
>     hbase_f *val_in = nullptr;        /* e.g., log() for log-based histogram */
>     hbase_f *val_out = nullptr;       /* e.g., exp() for log based histogram */
> }
> 
> For some reason this version of gcc considers val_in/val_out as
> methods.

They are function pointers, since hbase_f is a typedef of a function
that takes a double as argument and returns a double.

Indeed, the following minimal program:

typedef double hbase_f(double);

class StatHist
{
	hbase_f *val_in = nullptr;
};

fails to build with gcc 4.7, but builds fine with a more recent gcc. It
would be good to find another gcc 4.7 toolchain to see if the same
problem occurs.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-10-11  8:39 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10  6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-10-09 Thomas Petazzoni
2018-10-10 15:48 ` [Buildroot] Analysis " Thomas Petazzoni
2018-10-10 16:28   ` Matthew Weber
2018-10-10 17:57     ` Fabrice Fontaine
2018-10-10 19:14       ` Thomas Petazzoni
2018-10-10 21:25         ` Matthew Weber
2018-10-11  6:50           ` Thomas Petazzoni
2018-10-11 13:35             ` Matthew Weber
2018-10-12  3:57             ` Matthew Weber
2018-10-12 14:16               ` Matthew Weber
2018-10-20 14:10                 ` Matthew Weber
2018-10-10 19:05     ` Thomas Petazzoni
2018-10-12 16:00     ` Matthew Weber
2018-10-10 21:30   ` Arnout Vandecappelle
2018-10-11  6:46     ` Thomas Petazzoni
2018-10-11  9:21     ` Peter Korsgaard
2018-10-11 21:32       ` Arnout Vandecappelle
2018-10-10 21:35   ` Arnout Vandecappelle
2018-10-12  6:54     ` Jörg Krause
2018-10-10 21:52   ` Christian Stewart
2018-10-10 21:54   ` Arnout Vandecappelle
2018-10-11  4:43   ` Baruch Siach
2018-10-11  6:53     ` Thomas Petazzoni
2018-10-11  9:48       ` Peter Korsgaard
2018-10-11 14:12         ` Thomas Petazzoni
2018-10-11 15:25           ` Peter Korsgaard
2018-10-11  8:39     ` Thomas Petazzoni [this message]
2018-10-11 10:42     ` Peter Korsgaard
2018-10-11 11:08       ` Baruch Siach
2018-10-11 11:18         ` Peter Korsgaard
2018-10-11 11:45           ` Baruch Siach
2018-10-11 12:46             ` Peter Korsgaard
2018-10-11 11:02   ` Giulio Benetti
2018-10-20 15:22     ` Giulio Benetti
2018-10-11 14:31   ` Frank Hunleth
2018-10-11 14:32     ` Thomas Petazzoni
2018-10-11 19:24   ` Giulio Benetti

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=20181011103915.69e80d88@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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