isl 0.18 is the supported version for gcc 8 branch.
Original message
From: freddie_chopin at op dot pl
Date: 08/08/2018 16:04 (GMT+00:00)
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/86890] New: GCC 8.2.0 fails to build with isl 0.20
I resent change causes ada no longer to bootstrap
multiple definition of ada_demangle
/usr/local/src/gcc4.3/src/libiberty/cplus-dem.c:895: multiple definition
of `ada_demangle'
ada/adadecode.o:/usr/local/src/gcc4.3/src/gcc/ada/adadecode.c:374: first
defined here
graham
All,
I noticed that files in the c-family directory compiled during stage3 arn't
using -Werror along
with many other Warning flags usually applied during stage3
This to me appears to be because nothing is definng c-family-warn =
$(STRICT_WARN) so
any warnings specified as parrt of
All,
nested functions get passed a hidden argumment akin to static link/display
so that nested function can access the locals of its enclosing function.
Passing a nested function as parameter to another function isn't going
to work correctly when the function is eventually called the
hidden
Richard,
const volatile is a perfectly valid combination.
What is says is it's read only but may change value in ways unknown to the
compiler think of a memory mapped hardware register which is read only such as
some kind of counter .
Cheers
Graham
Hi Richard,
Does this patch work for objects which are both const and volatile
get_symbol_constant_value only looks at TREE_READONLY should it not
also look at TREE_VOLATILE ?
I don't have a upto date tree to hand to try the following testcase on
static const volatile int value = 42;
int
All,
From the backtrace I very doubt this is a IRA issue.
I looks to be related to the recent IPA/CGRAPG changes
so it's one for Honza to look at
Cheers
Graham
All,
Not a bug in GCC the result is correct as you've only asked for a 32-bit
multiply.
--- Hans Petter Selasky [EMAIL PROTECTED] wrote:
Test program:
#include stdio.h
#include sys/types.h
int main() {
int32_t a = 0x4000;
int16_t b = 0x4000;
All,
Not a bug, this is yet another case of type pruning.
Use -fno-strict-aliasing or fix your code.
Graham
All,
Not a bug, this is yet another case of type pruning.
Use -fno-strict-aliasing or fix your code.
Graham
All,
If the warning isn't bogus then we probably need to do the shift in two steps
(i.e. hwi = (hwi (shift - 1)) 1) as done elsewhere to avoid the
potential warning.
--- joseph at codesourcery dot com [EMAIL PROTECTED] wrote:
--- Comment #4 from joseph at codesourcery dot com
ghazi at gcc dot gnu dot org wrote:
I'm getting an RTL checking bootstrap failure on i686-unknown-linux-gnu. The
bootstrap dies in stage2 like so:
/home/ghazi/tmpdisk/gcc-testing/42/build/./prev-gcc/xgcc
-B/home/ghazi/tmpdisk/gcc-testing/42/build/./prev-gcc/
-B/usr/local/i686-pc-linux-gnu/bin/
ghazi at gcc dot gnu dot org wrote:
--- Comment #2 from ghazi at gcc dot gnu dot org 2005-12-26 16:04 ---
I did a successful rtl bootstrap (--enable-checking=yes,rtl) as recently as:
http://gcc.gnu.org/ml/gcc-testresults/2005-12/msg00388.html
So this is at most a few weeks old.
It
nathan at gcc dot gnu dot org wrote:
--- Additional Comments From nathan at gcc dot gnu dot org 2005-06-18
13:04 ---
can someone send me the .i file and/or sys/ucontext.h, I don't have an x86-64
system available.
It also happens on i686-pc-linux-gnu
All,
FWIW here's a quick patch which fixes bootstrap problem for me on i686-pc-linux-gnu.
I've got to go out the door in 5 mins do with as you see fit.
Graham
Index: intrinsic.c
15 matches
Mail list logo
