Hi!
The following bug has been introduced when cond_expr_object_size has been
added in 2007. We want to treat a COND_EXPR like a PHI with 2 arguments,
and PHI is handled in a loop that breaks if the lhs value is unknown, and
then does the if (TREE_CODE (arg) == SSA_NAME) merge_object_sizes else
e
On Thu, 17 Oct 2019, Jakub Jelinek wrote:
> Hi!
>
> The following bug has been introduced when cond_expr_object_size has been
> added in 2007. We want to treat a COND_EXPR like a PHI with 2 arguments,
> and PHI is handled in a loop that breaks if the lhs value is unknown, and
> then does the if
On 10/17/19 1:00 AM, Jakub Jelinek wrote:
Hi!
The following bug has been introduced when cond_expr_object_size has been
added in 2007. We want to treat a COND_EXPR like a PHI with 2 arguments,
and PHI is handled in a loop that breaks if the lhs value is unknown, and
then does the if (TREE_CODE
On Thu, Oct 17, 2019 at 06:07:37PM -0600, Martin Sebor wrote:
> On 10/17/19 1:00 AM, Jakub Jelinek wrote:
> > Hi!
> >
> > The following bug has been introduced when cond_expr_object_size has been
> > added in 2007. We want to treat a COND_EXPR like a PHI with 2 arguments,
> > and PHI is handled i
On 10/18/19 12:52 AM, Jakub Jelinek wrote:
On Thu, Oct 17, 2019 at 06:07:37PM -0600, Martin Sebor wrote:
On 10/17/19 1:00 AM, Jakub Jelinek wrote:
Hi!
The following bug has been introduced when cond_expr_object_size has been
added in 2007. We want to treat a COND_EXPR like a PHI with 2 argume