Hello,
looking at the changes for configuration in gcc 9.1, I noticed:
1) New configure options
OTOOL/OTOOL_FOR_TARGET: Which I assume from google is the Darwin ldd
replacement
GDC_FOR_TARGET: Which with a bit of guess work I assume is the
Gnu_D_Compiler
Is this stuff documented anywhere?
factor.
2) It would be nice to see some sort of out of memory error, rather than
just an ICE.
The system has 858Mb of RAM without the swap file.
Building a single source file seems to use up to 97% of the available
memory (for a 2522 line C++ source file).
make -j2 is enough to cause the failure.
Regards
Andrew Roberts
On 09/08/17 14:05, Andrew Roberts wrote:
I routinely build the weekly snapshots and RC's, on x64, arm and aarch64.
The last gcc 8 snapshot and the two recent 7.2 RC's have failed to
build on aarch64 (Raspberry Pi 3, running Arch Linux ARM). I have
finally traced this to the system r
On 11/08/17 02:09, Pedro Alves wrote:
Meanwhile, maybe just having the driver check for SIGKILL and
enumerate likely causes would be better than the status quo.
Pedro Alves
I agree, having some indication it MIGHT be out of memory would stop
people wasting a lot of time, and avoid spurious bu
On 10/08/17 10:22, Richard Earnshaw (lists) wrote:
If you think gcc is using an unreasonable amount of memory for a
particular bit of code then please file a bug report, with pre-processed
source code (don't assume that because the sources are part of gcc we
can reproduce your setup). You should
I've updated this bug [Bug 81818 - aarch64 uses 2-3x memory and 2x time
of arm at -Os, -O2, -O3] with more info.
It looks to be that on ARM systems with limited RAM optimizations are
being skipped, but not on AARCH64.
Is there a way I can check this is true?
I checked all the optimizations e
I was adding a comment to bug:
81616 - Update -mtune=generic for the current Intel and AMD processors
After clicking add comment it took me an an entirely different bug.
I tried to add the comment again, and got a message about a "Mid Air
Collision"
The comment ended up the system twice (Com
Its not my first bug, I've had plenty. But the first since the last
bugzilla crash a couple of months ago.
Perhaps the recovery from that altered the default or changed my account
setup. I've now reset it.
Part of my last bug was lost in the last crash, so I was just feeling
paranoid.
Thanks
MPFR 4.0.0-rc1 causes in-tree build of gcc to fail (error building mpc)
Using:
gcc-8-20171203
gmp 6.1.2
mpc 1.0.3
mpfr 4.0.0-rc1
isl 0.16.1
mpfr-3.1.6 works fine.
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I../../../gcc-8.0.0/mpc/src -I.. -I/home/aroberts/gcc/gcc-bu
I've tested building:
gcc version 8.0.0 20171210 (experimental) (GCC)
With the following in tree:
gmpver=6.1.2
mpfrver=4.0.0-rc1
mpcver=1.1-rc1
islver=0.16.1
This now works fine on:
x86_64-unknown-linux-gnu
armv7l-unknown-linux-gnueabihf
aarch64-unknown-linux-gnu
x86_64-apple-darwin17.3
Boot strap on Darwin x86_64 with llvm now seems broken as of last 8.0.0
snapshot, it still is working fine with 7.2.0.
I've added bug: 83903
x86_64, armv6, armv7, aarch64 all seem fine on linux. I've been building
with latest gmp (6.1.2), mpfr (4.0.0) and mpc (1.1.) across all my systems.
I o
It might be worth checking what MPFR is linking with in the test suite.
I seemed to see it
linking with the system libs when built in tree, rather than the in tree
ones.
This seems a regression in the MPFR test suite compared with 3.1.6
Andrew
On 26/01/18 14:22, Rainer Orth wrote:
I've given
I filed a bug (85578) about the documentation in:
gcc-8.0.1-RC-20180427/INSTALL
being broken (links not working).
I filed this under 'web' as I couldn't see any documentation component.
It doesn't appear to have been looked at,
so just wanted to flag it up before the release tomorrow.
The reason I was looking at the versions in the RC tarball was that I
have never been clear as to what release the website
install/prerequisite/target info actually applies to.
It would be much better if this info was on a per release basis on the
web site, like the changelog and manuals. Thus a
14 matches
Mail list logo
