* Romain Geissler:
> That may fly in the open source world, however I expect some vendors
> shipping proprietary code might be fine with assembly/LTO
> representation of their product, but not source.
They can't ship LTO today anyway due to the format incompatibility, so
that's not really an argu
Hi Devs,
consider below reduced testcase from boost lamda.
$cat result_of_tests.cpp
#include
#include
template typename boost::result_of::type apply1(F
f, A b) {
return f(b);
}
using namespace boost::lambda;
int main(int, char *[]) {
int one = 1;
int d= (apply1(_1 ,one) == 1);
pri
For MSP430, the folding of identical functions marked with the "interrupt"
attribute by -fipa-icf-functions results in wrong code being generated.
Interrupts have different calling conventions than regular functions, so
inserting a CALL from one identical interrupt to another is not correct and
wil
On Fri, 19 Jul 2019, Jozef Lawrynowicz wrote:
> For MSP430, the folding of identical functions marked with the "interrupt"
> attribute by -fipa-icf-functions results in wrong code being generated.
> Interrupts have different calling conventions than regular functions, so
> inserting a CALL from on
Snapshot gcc-8-20190719 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/8-20190719/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-8
I have seen an increasing number of reports of GCC failing to
build with clang on powerpc (on FreeBSD, though that's probably
immaterial).
Turns out that clang has vec_step as a reserved word on powerpc
with AltiVec.
We OTOH use vec_step s as a variable name in gcc/tree-vect-loop.c.
The best ap
