Configuring GCC for obsolete targets works as long as build = host.
When it isn't, --enable-obsolete is not passed down to the additional
build configure started by gcc/configure, used to generate
auto-build.h. The build configure fails and we end up without a
auto-build.h, but the host configure
Committed.
Gerald
- Log -
commit 0f32e95bf23411b8247c122588bfd14079b93ed0
Author: Gerald Pfeifer
Date: Sat Nov 2 21:24:24 2019 +
Switch www.adapteva.com to https.
diff --git a/htdocs/readings.html b/htdocs/readings.html
On Oct 30, 2019, Richard Biener wrote:
> One way of operation would be to
> generate the graph during the compilation step
Stack usage is only computed during prologue/epilogue generation in RTL.
> Additional arguments to -fcallgraph-info might be used to direct the
> output to a specific direc
This breaks bootstrap on powerpc:
/daten/gcc/gcc-20191101/Build/./prev-gcc/xg++
-B/daten/gcc/gcc-20191101/Build/./prev-gcc/ -B/usr/powerpc64-suse-linux/bin/
-nostdinc++
-B/daten/gcc/gcc-20191101/Build/prev-powerpc64-suse-linux/libstdc++-v3/src/.libs
-B/daten/gcc/gcc-20191101/Build/prev-powerp
The AMD GCN architecture uses 64-bit pointers, but the scalar registers
are 32-bit wide, so pointers must reside in a pair of registers.
The two hard registers holding the frame pointer are currently fixed,
but if they are changed to unfixed (so that the FP can be eliminated),
GCC would someti
Hi Jakub:
Could you help reviewing this patch.
PS: Since this patch is related to vectors(avx512f), and Uros
mentioned before that he has no intension to maintain avx512f.
On Fri, Nov 1, 2019 at 9:12 AM Hongtao Liu wrote:
>
> Hi uros:
> This patch is about to fix inefficient vector construct
Hello world,
the attached patch fixes an 8/9/10 regression where, to fix PR 84487
by not putting the initializers and vtabs into the read-only section
(for reasons of size, which could grow enormously) led to a regression
on POWER9 and other non-x86 architectures, where the initializer was
someti
Hi!
The following patch implements the scoring, except it doesn't handle the
case when a call is nested in 188+ OpenMP constructs yet.
At least in the current standard wording, the score can be a sum of
up to 8 2^X numbers where X is quite arbitrary constant (because the
construct nesting depth c
