Hi,
I ran into a problem that C frontend (in function
build_conditional_expr) creates expression like (C_MAYBE_CONST_EXPR
(NULL, x + const)). The inner expression (and its operands) have
unsigned int type. After that, the expression needs to be casted to
result type which is unsigned short. In t
On 24 July 2016 at 21:26, Bin.Cheng wrote:
> Hi,
> I ran into a problem that C frontend (in function
> build_conditional_expr) creates expression like (C_MAYBE_CONST_EXPR
> (NULL, x + const)). The inner expression (and its operands) have
> unsigned int type. After that, the expression needs to b
Snapshot gcc-7-20160724 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20160724/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision
Hi,
I am trying to write a WIP patch to warn for dead function calls,
and incidentally it caught the following dead call to gimple_bb() from
slsr_process_phi () in gimple-ssa-strength-reduction.c:
if (SSA_NAME_IS_DEFAULT_DEF (arg))
arg_bb = single_succ (ENTRY_BLOCK_PTR_FOR_FN (cfun));
else